Triple
T37901678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Финляндский вокзал |
E945429
|
entity |
| Predicate | принадлежит |
P347
|
FINISHED |
| Object | Российские железные дороги |
—
|
NE NERFINISHED |
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.
надлежност
Indicates that one entity belongs to, is under the authority of, or falls within the responsibility or jurisdiction of another entity.
-
B.
appartientÀ
Indicates that one entity belongs to, is a member of, or is part of another entity.
-
C.
ownedBy
chosen
Indicates that one entity possesses legal or rightful ownership of another entity.
-
D.
believedToBelongTo
Indicates that something is thought or assumed, but not definitively known, to be owned by or part of a particular entity.
-
E.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
- 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.