Triple
T25220285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrandyte Fire Brigade |
E631942
|
entity |
| Predicate | emergencyTypeHandled |
P77203
|
FINISHED |
| Object | vehicle 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: vehicle fires | Statement: [Warrandyte Fire Brigade, emergencyTypeHandled, vehicle fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyTypeHandled Context triple: [Warrandyte Fire Brigade, emergencyTypeHandled, vehicle fires]
-
A.
emergencyTypesCovered
chosen
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
B.
emergencyCareLevel
Indicates the degree or intensity of medical attention required in an emergency situation.
-
C.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
-
D.
emergencyConcern
Indicates a relationship where one entity has an urgent, high-priority concern or issue about another entity or situation that may require immediate attention or action.
-
E.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:03 p.m.