Triple
T30770771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1981 |
E783516
|
entity |
| Predicate | USAircraftType |
P1524
|
FINISHED |
| Object | Grumman F-14 Tomcat |
—
|
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: Grumman F-14 Tomcat | Statement: [Gulf of Sidra incident 1981, USAircraftType, Grumman F-14 Tomcat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USAircraftType Context triple: [Gulf of Sidra incident 1981, USAircraftType, Grumman F-14 Tomcat]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
C.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
D.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
E.
typicalAircraftTypeCategory
Indicates the general class or category of aircraft type that is most commonly associated with or used in a given context.
- 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.