Triple
T27328034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daegu Metro Line 1 |
E689712
|
entity |
| Predicate | subwayFireCasualties |
P162189
|
FINISHED |
| Object | 192 deaths (approximate) |
—
|
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: 192 deaths (approximate) | Statement: [Daegu Metro Line 1, subwayFireCasualties, 192 deaths (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayFireCasualties Context triple: [Daegu Metro Line 1, subwayFireCasualties, 192 deaths (approximate)]
-
A.
tramwayDestroyedBy
Indicates that a tramway was damaged or rendered unusable as a direct result of an action or event caused by another entity.
-
B.
subwaySeries
Indicates a sports matchup or series played between two teams from the same metropolitan area, especially within the same city.
-
C.
subwayFireDate
chosen
Indicates the date on which a fire occurred in a subway system or subway-related context.
-
D.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
E.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627ef6bac8190a7edfb950c1ad3c4 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:36 a.m.