Triple
T9221074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Civil Defense |
E221359
|
entity |
| Predicate | handlesIncidentType |
P76024
|
FINISHED |
| Object | building 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: building fires | Statement: [Egyptian Civil Defense, handlesIncidentType, building fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesIncidentType Context triple: [Egyptian Civil Defense, handlesIncidentType, building fires]
-
A.
notableIncidentType
chosen
Indicates the specific category or kind of significant event or incident associated with an entity.
-
B.
typeOfCrisisManagement
Indicates the specific approach or method used to manage, respond to, or resolve a crisis situation.
-
C.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
D.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
E.
hazardType
Indicates the specific kind or category of hazard associated with an entity or 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda75b6888190814cfb890e763b8f |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.