Triple
T31896473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City integrated fare system |
E814296
|
entity |
| Predicate | previousCardSystem |
P144347
|
FINISHED |
| Object | Tarjeta CDMX |
—
|
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: Tarjeta CDMX | Statement: [Mexico City integrated fare system, previousCardSystem, Tarjeta CDMX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCardSystem Context triple: [Mexico City integrated fare system, previousCardSystem, Tarjeta CDMX]
-
A.
previousSystemName
chosen
Indicates that an entity was formerly known by a different system name prior to its current designation.
-
B.
previousCollection
Indicates that one collection directly precedes another in an ordered sequence or series.
-
C.
previousDenomination
Indicates that one entity was the earlier or former denomination (name, value, or classification) of another entity in a sequence of denominations.
-
D.
previousRecord
Indicates that one record directly precedes another in an ordered sequence of records.
-
E.
previousBanknoteSeries
Indicates that one banknote series directly precedes another in the chronological sequence of issued banknote series.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 30, 2026, 11:59 p.m.