Triple
T37901651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Финляндский вокзал |
E945429
|
entity |
| Predicate | имеетАдрес |
P4379
|
FINISHED |
| Object | площадь Ленина, Санкт-Петербург |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: площадь Ленина, Санкт-Петербург | Statement: [Финляндский вокзал, имеетАдрес, площадь Ленина, Санкт-Петербург]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетАдрес Context triple: [Финляндский вокзал, имеетАдрес, площадь Ленина, Санкт-Петербург]
-
A.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
B.
hasAddressRole
Indicates that a specific role or function is associated with an address within a given context (e.g., billing, shipping, primary).
-
C.
addressedWith
Indicates that one entity is referred to or spoken to using a particular name, title, or form of address.
-
D.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:20 p.m.