Triple

T34711686
Position Surface form Disambiguated ID Type / Status
Subject Doroteo Jose station E1000663 entity
Predicate fareControlRelationship P181804 FINISHED
Object out-of-system transfer to Recto station LITERAL FINISHED

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: out-of-system transfer to Recto station | Statement: [Doroteo Jose station, fareControlRelationship, out-of-system transfer to Recto station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareControlRelationship
Context triple: [Doroteo Jose station, fareControlRelationship, out-of-system transfer to Recto station]
  • A. fareRelationship
    Indicates a relationship between entities based on the cost, pricing, or fare charged for a service or trip.
  • B. fareControlUnifiedWith
    Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
  • C. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • D. ownershipRelation
    Indicates that one entity possesses legal or recognized ownership rights over another entity.
  • E. trackRelationship
    Indicates a connection in which one entity monitors, follows, or keeps a record of another entity’s state, behavior, or changes over time.
  • 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_69f76dad3f108190a280fd0a2f4ee89a completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7824dc3f0819092a5102895b4a478 completed May 3, 2026, 5:13 p.m.
PD Predicate disambiguation batch_69f780fc5ed88190b7200ee5a29940af completed May 3, 2026, 5:08 p.m.
PDg Predicate description generation batch_69f7817c79e081908e685c48165e086b completed May 3, 2026, 5:10 p.m.
Created at: May 3, 2026, 3:59 p.m.