Triple
T19175528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Camp Fire |
E469426
|
entity |
| Predicate | femaDisasterNumber |
P134737
|
FINISHED |
| Object | 4407 |
—
|
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: 4407 | Statement: [2018 Camp Fire, femaDisasterNumber, 4407]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: femaDisasterNumber Context triple: [2018 Camp Fire, femaDisasterNumber, 4407]
-
A.
emergencyPhoneNumber
Indicates that the object is a phone number designated for use in emergencies or urgent situations.
-
B.
operatesNonEmergencyNumber
Indicates that an entity is responsible for running or managing a telephone number designated for non-emergency inquiries or services.
-
C.
operatesEmergencyNumber
Indicates that an entity is responsible for running or managing an emergency telephone number service for another entity or region.
-
D.
usesEmergencyNumber
Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
-
E.
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.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f166d3888190adaf6dc8531a8ed1 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.