Triple
T38328661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha Metro Green Line |
E1036859
|
entity |
| Predicate | isPartOfNetworkWithLine |
P201886
|
FINISHED |
| Object | Doha Metro Red Line |
—
|
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: Doha Metro Red Line | Statement: [Doha Metro Green Line, isPartOfNetworkWithLine, Doha Metro Red Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNetworkWithLine Context triple: [Doha Metro Green Line, isPartOfNetworkWithLine, Doha Metro Red Line]
-
A.
identifiesStationWithinLine
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
-
B.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
C.
connectsToMetroLineAt
Indicates that one location or transportation facility is directly linked or provides access to a specific metro line at a particular point.
-
D.
isOnPassengerNetwork
Indicates that an entity is part of, connected to, or operates within a passenger transportation network.
-
E.
isBetweenStationsOnLine
Indicates that something is located or occurs between two stations along the same transit line.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_6a002e706dfc8190bbf2bc230f537e83 |
completed | May 10, 2026, 7:06 a.m. |
Created at: May 3, 2026, 4:30 p.m.