Triple
T34581101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Central Diameters |
E887902
|
entity |
| Predicate | MCD-2Connects |
P179338
|
FINISHED |
| Object | Nakhabino and Podolsk |
—
|
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: Nakhabino and Podolsk | Statement: [Moscow Central Diameters, MCD-2Connects, Nakhabino and Podolsk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCD-2Connects Context triple: [Moscow Central Diameters, MCD-2Connects, Nakhabino and Podolsk]
-
A.
hasNumberOfCables
Indicates the relationship that specifies how many cables are associated with a given entity.
-
B.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
C.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
D.
connectorDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a connector used to link or interface components.
-
E.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c32a60819083bd47b9b1903ebc |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:03 a.m.