Triple
T22316724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel Bridge |
E551663
|
entity |
| Predicate | causeOf1993Fire |
P147720
|
FINISHED |
| Object | likely discarded cigarette |
—
|
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: likely discarded cigarette | Statement: [Chapel Bridge, causeOf1993Fire, likely discarded cigarette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOf1993Fire Context triple: [Chapel Bridge, causeOf1993Fire, likely discarded cigarette]
-
A.
firstBuildingDestroyedByFire
Indicates that the first building in a given context was destroyed as a result of a fire.
-
B.
destroyedByFire
Indicates that something has been ruined, damaged, or rendered unusable as a direct result of a fire.
-
C.
fireIncidentRelated
Indicates that there is a connection or association between a specific fire incident and another entity, event, or record.
-
D.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
E.
fireBeganAt
Indicates that the event of a fire starting occurred at a specific time or location.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157535eb48190adbefbb619cb5fcd |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:42 p.m.