Triple
T30887882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City light rail |
E786815
|
entity |
| Predicate | mainLineName |
P28725
|
FINISHED |
| Object | Xochimilco Light Rail |
—
|
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: Xochimilco Light Rail | Statement: [Mexico City light rail, mainLineName, Xochimilco Light Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLineName Context triple: [Mexico City light rail, mainLineName, Xochimilco Light Rail]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
lineName
chosen
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
-
C.
formerLineName
Indicates that the object is a previous or former name by which the referenced line was known.
-
D.
connectsToMainLineAt
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
E.
primaryMarketedRouteName
Indicates the main route or method by which a product is marketed or delivered to its intended users.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:49 p.m.