Triple

T20025040
Position Surface form Disambiguated ID Type / Status
Subject Zone 12 E494957 entity
Predicate fareRelationship P138412 FINISHED
Object used for fares to and from certain stations 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: used for fares to and from certain stations | Statement: [Zone 12, fareRelationship, used for fares to and from certain stations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fareRelationship
Context triple: [Zone 12, fareRelationship, used for fares to and from certain stations]
  • A. addressesRelationship
    Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
  • B. parentRelationship
    Indicates a familial relationship in which one entity is the parent of another entity.
  • C. basisOfRelationship
    Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
  • D. familyConnectionTo
    Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
  • E. establishedRelationship
    Indicates that a formal, recognized relationship has been created and is now in effect between the referenced entities.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6628b6b7c81909a660fbec9c92295 completed April 20, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69e54ce752748190a0a1ffddd0372271 completed April 19, 2026, 9:45 p.m.
PDg Predicate description generation batch_69e54fc20888819083c9118a09d0d2dc completed April 19, 2026, 9:57 p.m.
Created at: April 11, 2026, 3:35 p.m.