Triple

T25402039
Position Surface form Disambiguated ID Type / Status
Subject Foxton railway station E636448 entity
Predicate hasEmergencyTelephone P159437 FINISHED
Object yes 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: yes | Statement: [Foxton railway station, hasEmergencyTelephone, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyTelephone
Context triple: [Foxton railway station, hasEmergencyTelephone, yes]
  • A. hasNonEmergencyNumber
    Indicates that an entity is associated with a phone number intended for non-emergency, routine, or informational contact rather than urgent or emergency situations.
  • B. emergencyPhoneNumber
    Indicates that the object is a phone number designated for use in emergencies or urgent situations.
  • C. usesEmergencyNumber
    Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
  • D. hasEmergencyServices
    Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
  • E. operatesEmergencyNumber
    Indicates that an entity is responsible for running or managing an emergency telephone number service for another entity or region.
  • 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_69e75db361d881908d8701c856da6413 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f584fa51c481909a8f11b41f2b1d30 completed May 2, 2026, 5 a.m.
PD Predicate disambiguation batch_69f4a0f7c6008190ae8cee3e71e19b94 completed May 1, 2026, 12:47 p.m.
PDg Predicate description generation batch_69f55e497fa081909bc59a7b92c5df59 completed May 2, 2026, 2:15 a.m.
Created at: April 21, 2026, 1:52 p.m.