Triple
T7574372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OV-099 |
E179324
|
entity |
| Predicate | crewKilledInAccident |
P29707
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [OV-099, crewKilledInAccident, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewKilledInAccident Context triple: [OV-099, crewKilledInAccident, 7]
-
A.
crewFatality
chosen
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
B.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
C.
aircraftInvolvedInDeath
Indicates that an aircraft played a direct role in causing or contributing to a person's death.
-
D.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
E.
astronautFatalities
Indicates that the situation or event involves the death of one or more astronauts.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.