Triple
T14569354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindenburg disaster |
E341868
|
entity |
| Predicate | killedOnGround |
P114710
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Hindenburg disaster, killedOnGround, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedOnGround Context triple: [Hindenburg disaster, killedOnGround, 1]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
killedOnBoard
Indicates that one entity caused the death of another entity while they were on a vehicle, vessel, or similar conveyance.
-
C.
killedOrMortallyWounded
Indicates that one entity caused the death of, or inflicted injuries certain to result in the death of, another entity.
-
D.
killedAt
Indicates that a killing event occurred at a specific location or time associated with the entities involved.
-
E.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.