Triple

T31896472
Position Surface form Disambiguated ID Type / Status
Subject Mexico City integrated fare system E814296 entity
Predicate usesCard P192502 FINISHED
Object Tarjeta de Movilidad Integrada 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 de Movilidad Integrada | Statement: [Mexico City integrated fare system, usesCard, Tarjeta de Movilidad Integrada]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCard
Context triple: [Mexico City integrated fare system, usesCard, Tarjeta de Movilidad Integrada]
  • A. containsCard
    Indicates that one entity includes or holds a specific card as part of its contents or collection.
  • B. legalCardsFrom
    Indicates that the referenced cards are permitted or valid according to the rules or constraints defined by the specified source or authority.
  • C. cardEffect
    Indicates that one card produces a specific effect or outcome on another entity or the game state.
  • D. isSupercardOf
    Indicates that one card or set of cards fully contains or extends the content, scope, or functionality of another card, making it a more comprehensive or encompassing version.
  • E. cardText
    Indicates that one entity is the textual content displayed on a card associated with another entity.
  • 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_69f348ef817481908440e2250319bcc8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd0d0ba5c48190bddb3f0e6637544c completed May 7, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69fd0c4324a8819086c90adf46216e0e completed May 7, 2026, 10:03 p.m.
PDg Predicate description generation batch_69fd0d0aebac8190868a7714ddb4f1fd completed May 7, 2026, 10:07 p.m.
Created at: April 30, 2026, 11:59 p.m.