Triple

T23090725
Position Surface form Disambiguated ID Type / Status
Subject Troy Fire Department E575739 entity
Predicate hasPublicContactMethod P77037 FINISHED
Object non-emergency phone line 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: non-emergency phone line | Statement: [Troy Fire Department, hasPublicContactMethod, non-emergency phone line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPublicContactMethod
Context triple: [Troy Fire Department, hasPublicContactMethod, non-emergency phone line]
  • A. hasContactMethod
    Indicates that an entity has a specific way or channel through which it can be contacted.
  • B. hasNonEmergencyNumber chosen
    Indicates that an entity is associated with a phone number intended for non-emergency, routine, or informational contact rather than urgent or emergency situations.
  • C. hasContactRole
    Indicates that an entity serves in a specific role or capacity as a contact for another entity.
  • D. hasContactState
    Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
  • E. hasCommunicationAccess
    Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
  • 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da99bec81908ecadf8dab10d1b7 completed April 29, 2026, 4:48 a.m.
PD Predicate disambiguation batch_69ef89e5ce748190b2c3ac3843484127 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 3:57 p.m.