Triple
T5247174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fritz Todt |
E118489
|
entity |
| Predicate | aircraftAccidentInvolved |
P32122
|
FINISHED |
| Object | Heinkel He 111 crash |
—
|
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: Heinkel He 111 crash | Statement: [Fritz Todt, aircraftAccidentInvolved, Heinkel He 111 crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftAccidentInvolved Context triple: [Fritz Todt, aircraftAccidentInvolved, Heinkel He 111 crash]
-
A.
aircraftInvolvedInDeath
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
B.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
C.
involvedInAccident
chosen
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
D.
aircraftImpact
Indicates that an aircraft collides with or crashes into a target or surface, causing an impact event.
-
E.
airlineInvolved
Indicates that a specific airline is directly associated with, or plays a role in, a particular event, situation, or context.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b5320748190bcf3be4b6c364f92 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.