Triple
T31686379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 1 (Mexico City Metrobús) |
E808672
|
entity |
| Predicate | inauguralLineOf |
P172419
|
FINISHED |
| Object | Mexico City Metrobús |
—
|
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: Mexico City Metrobús | Statement: [Line 1 (Mexico City Metrobús), inauguralLineOf, Mexico City Metrobús]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralLineOf Context triple: [Line 1 (Mexico City Metrobús), inauguralLineOf, Mexico City Metrobús]
-
A.
inauguralEvent
Indicates that an event is the first in a series or marks the formal beginning of a recurring activity, program, or institution.
-
B.
hasInauguralAddress
Indicates that an entity delivered or is associated with a formal inaugural address, typically marking the beginning of an official term or position.
-
C.
inauguralHolder
Indicates that the subject is the first person or entity to hold a particular position, title, office, or role.
-
D.
inauguralName
Indicates the name or title originally given to something at its inception or first occurrence.
-
E.
inauguralSection
Indicates the section or part of a work that serves as its formal beginning or opening.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:06 p.m.