Triple
T30861883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1986 |
E786080
|
entity |
| Predicate | aircraftUsedByLibya |
P173426
|
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 1986, aircraftUsedByLibya, Sukhoi Su-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftUsedByLibya Context triple: [Gulf of Sidra incident 1986, aircraftUsedByLibya, Sukhoi Su-22]
-
A.
aircraftUsedByRussia
Indicates that the aircraft is operated, deployed, or otherwise utilized by Russia.
-
B.
LibyanAircraftLost
Indicates that a Libyan aircraft has been lost, typically through destruction, disappearance, or being rendered inoperable.
-
C.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
D.
aircraftUsedByCondorLegion
Indicates that an aircraft was used operationally by the Condor Legion.
-
E.
notableAircraftUsed
Indicates that an entity is known for using, operating, or being associated with a particular aircraft in a notable or significant way.
- F. None of above. chosen
Provenance (4 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 29, 2026, 8:47 p.m.