Triple
T2069794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyublinsko–Dmitrovskaya Line |
E45988
|
entity |
| Predicate | isUnderground |
P15152
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lyublinsko–Dmitrovskaya Line, isUnderground, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnderground Context triple: [Lyublinsko–Dmitrovskaya Line, isUnderground, true]
-
A.
hasUndergroundSection
chosen
Indicates that an entity includes a portion or segment that is located below ground level.
-
B.
nearUndergroundLine
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
C.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
D.
hasUndergroundSlide
Indicates that one entity features or includes an underground slide connecting it to another location or structure.
-
E.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f677108190aea3c8db7850c892 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.