Triple
T30770774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1981 |
E783516
|
entity |
| Predicate | USAircraftLost |
P685
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Gulf of Sidra incident 1981, USAircraftLost, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USAircraftLost Context triple: [Gulf of Sidra incident 1981, USAircraftLost, 0]
-
A.
aircraftLostByUnitedStates
chosen
Indicates that an aircraft was lost (e.g., destroyed, missing, or otherwise no longer operational) and that this loss is attributed to the United States.
-
B.
aircraftLostByAllies
Indicates that the specified aircraft was lost by Allied forces (e.g., destroyed, missing, or otherwise no longer operational under their control).
-
C.
survivingAircraftLocation
Indicates the location where an aircraft that has survived an incident or event is situated.
-
D.
aircraftLostByJapan
Indicates that the specified aircraft were lost by Japan, typically through destruction, damage beyond repair, or disappearance.
-
E.
aircraftLosses
Indicates the number or occurrence of aircraft that have been destroyed, damaged beyond repair, or otherwise lost.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc1913081909b621a90cb555115 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:40 p.m.