Triple
T14681878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 129 Hindenburg |
E344805
|
entity |
| Predicate | crewFatalitiesInFinalAccident |
P29707
|
FINISHED |
| Object | 22 |
—
|
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: 22 | Statement: [LZ 129 Hindenburg, crewFatalitiesInFinalAccident, 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewFatalitiesInFinalAccident Context triple: [LZ 129 Hindenburg, crewFatalitiesInFinalAccident, 22]
-
A.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
B.
crewFatality
chosen
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
C.
pilotAtFatalCrash
Indicates that the specified person was serving as the pilot at the time and location of a fatal crash.
-
D.
crewComplementAtSinking
Indicates the number or composition of a vessel’s crew present on board at the time it sank.
-
E.
casualtiesHijackers
Indicates that the hijackers caused or were responsible for casualties (deaths or injuries) among others.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.