Triple
T6786091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santo Domingo Metro |
E155805
|
entity |
| Predicate | line2Orientation |
P42939
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Santo Domingo Metro, line2Orientation, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line2Orientation Context triple: [Santo Domingo Metro, line2Orientation, east–west]
-
A.
lineOrientation
chosen
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
B.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
C.
orientedParallelTo
Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
-
D.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
E.
orientationOfCross
Indicates the spatial orientation or alignment of a cross relative to a reference frame or object.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28f043081909a9a9ab635785933 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.