Triple
T24192435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strike Fighter Tactics Instructor program |
E599735
|
entity |
| Predicate | typeOfTactics |
P30685
|
FINISHED |
| Object | beyond-visual-range air combat |
—
|
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: beyond-visual-range air combat | Statement: [Strike Fighter Tactics Instructor program, typeOfTactics, beyond-visual-range air combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTactics Context triple: [Strike Fighter Tactics Instructor program, typeOfTactics, beyond-visual-range air combat]
-
A.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
B.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
D.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
E.
tacticInspiredBy
Indicates that a tactic is derived from, influenced by, or modeled after another tactic or source.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.