Triple
T25805508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daegu subway fire |
E649957
|
entity |
| Predicate | fireSpreadTo |
P159288
|
FINISHED |
| Object | second train in station |
—
|
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: second train in station | Statement: [Daegu subway fire, fireSpreadTo, second train in station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireSpreadTo Context triple: [Daegu subway fire, fireSpreadTo, second train in station]
-
A.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
B.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
C.
fireShape
Indicates that one entity has the specified geometric or visual form of a fire or flame.
-
D.
fireCoverage
Indicates the extent to which an area or object is protected or served by fire prevention, detection, or suppression resources.
-
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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffcee8288190b03d20d2f1f8df3d |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:02 a.m.