Triple
T13355311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastchester Fire District |
E318674
|
entity |
| Predicate | handlesEmergencyType |
P77203
|
FINISHED |
| Object | structure fires |
—
|
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: structure fires | Statement: [Eastchester Fire District, handlesEmergencyType, structure fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesEmergencyType Context triple: [Eastchester Fire District, handlesEmergencyType, structure fires]
-
A.
typeOfEmergencyService
Indicates the specific category or kind of emergency service associated with or provided in a given situation.
-
B.
emergencyTypesCovered
chosen
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
C.
hasEmergencyLevel
Indicates that an entity is associated with a specific degree or severity of emergency status.
-
D.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
-
E.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99f1ef94c81909a59b7c3f77d3335 |
completed | April 11, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.