Triple
T37901664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Финляндский вокзал |
E945429
|
entity |
| Predicate | построенДля |
P59941
|
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.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
-
B.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
-
C.
построенПоВремеНа
Indicates that something was built or constructed during the time period of a specified event, era, or ruler.
-
D.
builtStructureFor
chosen
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
E.
builtUpBy
Indicates that something has been constructed, developed, or formed through the actions or contributions of a specified agent or process.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.