Triple

T26746232
Position Surface form Disambiguated ID Type / Status
Subject Brooklyn and Staten Island E674409 entity
Predicate shareEmergencyNumber P37309 FINISHED
Object 911 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: 911 | Statement: [Brooklyn and Staten Island, shareEmergencyNumber, 911]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareEmergencyNumber
Context triple: [Brooklyn and Staten Island, shareEmergencyNumber, 911]
  • A. hasEmergencyTelephone
    Indicates that an entity is equipped with or provides access to an emergency telephone for urgent communication or assistance.
  • B. emergencyPhoneNumber chosen
    Indicates that the object is a phone number designated for use in emergencies or urgent situations.
  • C. operatesEmergencyNumber
    Indicates that an entity is responsible for running or managing an emergency telephone number service for another entity or region.
  • D. 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.
  • E. usesEmergencyNumber
    Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
  • 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_69eecda63a3881908095c47900692e65 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: April 27, 2026, 3:51 a.m.