Triple
T28337644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caproni Ca.60 Noviplano |
E717720
|
entity |
| Predicate | pilotInCrashInjuryStatus |
P133513
|
FINISHED |
| Object | injured but survived |
—
|
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: injured but survived | Statement: [Caproni Ca.60 Noviplano, pilotInCrashInjuryStatus, injured but survived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotInCrashInjuryStatus Context triple: [Caproni Ca.60 Noviplano, pilotInCrashInjuryStatus, injured but survived]
-
A.
pilotAtFatalCrash
Indicates that the specified person was serving as the pilot at the time and location of a fatal crash.
-
B.
injuryStatus
chosen
Indicates the condition or state of harm, damage, or physical injury affecting an entity.
-
C.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
-
D.
registrationStatusAfterAccident
Indicates the state of an entity’s registration following the occurrence of an accident.
-
E.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 12:37 a.m.