Triple
T33095329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagon |
E846892
|
entity |
| Predicate | subjectAircraftPrimaryRole |
P2860
|
FINISHED |
| Object | interceptor |
—
|
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: interceptor | Statement: [Flagon, subjectAircraftPrimaryRole, interceptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAircraftPrimaryRole Context triple: [Flagon, subjectAircraftPrimaryRole, interceptor]
-
A.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
B.
aircraftRoleDesignedFor
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
C.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
-
D.
aircraftRoleOfDesignatedAircraft
Indicates that an aircraft has the specified operational role or function as a designated aircraft within a particular context or mission.
-
E.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:26 a.m.