Triple
T30904120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Bright Fire Rescue |
E787246
|
entity |
| Predicate | hasTypeOfIncidentResponse |
P4217
|
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: [Sea Bright Fire Rescue, hasTypeOfIncidentResponse, structure fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfIncidentResponse Context triple: [Sea Bright Fire Rescue, hasTypeOfIncidentResponse, structure fires]
-
A.
hasEmergencyResponseEvent
Indicates that an entity is associated with a specific emergency response event that has occurred or been initiated.
-
B.
hasIncidence
Indicates that a particular event, condition, or phenomenon occurs at a certain rate, frequency, or number of cases within a defined population or context.
-
C.
commonIncidentType
Indicates that multiple entities share the same category or type of incident.
-
D.
hasTypeOfCase
chosen
Indicates that an entity is associated with or classified under a particular type or category of case.
-
E.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 29, 2026, 8:50 p.m.