Triple
T30770772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1981 |
E783516
|
entity |
| Predicate | LibyanAircraftType |
P1524
|
FINISHED |
| Object | Sukhoi Su-22 |
—
|
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: Sukhoi Su-22 | Statement: [Gulf of Sidra incident 1981, LibyanAircraftType, Sukhoi Su-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LibyanAircraftType Context triple: [Gulf of Sidra incident 1981, LibyanAircraftType, Sukhoi Su-22]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
C.
typeOfAviation
Indicates the specific category or kind of aviation to which an entity belongs (e.g., commercial, military, private).
-
D.
specificCarrierAircraftVariant
Indicates that one aircraft variant is a specific version designed or adapted for carrier-based operations of another, more general aircraft variant.
-
E.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
- 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_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.