Triple
T33377357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolniki Metro Station |
E854670
|
entity |
| Predicate | systemStartRole |
P176825
|
FINISHED |
| Object | part of first stage of Moscow Metro |
—
|
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: part of first stage of Moscow Metro | Statement: [Sokolniki Metro Station, systemStartRole, part of first stage of Moscow Metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemStartRole Context triple: [Sokolniki Metro Station, systemStartRole, part of first stage of Moscow Metro]
-
A.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
B.
startupRole
Indicates that an entity holds a specific role or position within a startup organization.
-
C.
systemOperator
Indicates that one entity functions as the operator or controller responsible for running, managing, or overseeing the operation of a system.
-
D.
publicRoleStart
Indicates the point in time when an entity begins to hold or perform a particular public role or office.
-
E.
managementRoleStart
Indicates the date or point in time when an entity begins holding a particular management role or position.
- F. None of above. chosen
Provenance (4 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:35 a.m.