Triple
T33095342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagon |
E846892
|
entity |
| Predicate | subjectAircraftIntendedMission |
P110429
|
FINISHED |
| Object | airspace interception |
—
|
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: airspace interception | Statement: [Flagon, subjectAircraftIntendedMission, airspace interception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAircraftIntendedMission Context triple: [Flagon, subjectAircraftIntendedMission, airspace interception]
-
A.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
B.
aircraftSecondaryMission
chosen
Indicates the secondary mission or role that an aircraft is intended or configured to perform in addition to its primary mission.
-
C.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
aircraftRoleDesignedFor
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 1:26 a.m.