Triple
T13138276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | September 18 Incident |
E312141
|
entity |
| Predicate | typeOfExplosion |
P100269
|
FINISHED |
| Object | railway line explosion |
—
|
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: railway line explosion | Statement: [September 18 Incident, typeOfExplosion, railway line explosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExplosion Context triple: [September 18 Incident, typeOfExplosion, railway line explosion]
-
A.
explosionType
chosen
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
C.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
D.
explosivity
Indicates the degree to which something is prone to explode or cause an explosion under certain conditions.
-
E.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.