Triple
T36825820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airship Italia |
E910006
|
entity |
| Predicate | crewInvolvedInAccident |
P24309
|
FINISHED |
| Object | Umberto Nobile |
—
|
NE NERFINISHED |
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: Umberto Nobile | Statement: [Airship Italia, crewInvolvedInAccident, Umberto Nobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewInvolvedInAccident Context triple: [Airship Italia, crewInvolvedInAccident, Umberto Nobile]
-
A.
crewInvolvedIn
chosen
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
B.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
C.
coPassengerInFatalCrashWith
Indicates that two or more individuals were passengers in the same vehicle involved in a fatal crash.
-
D.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
E.
accidentInvolvedAircraft
Indicates that an aircraft was directly involved in an accident or incident.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9c9ef88190b71bcc6f5b4a6182 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.