Triple
T34124780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxhound |
E875243
|
entity |
| Predicate | natoNameCategory |
P72828
|
FINISHED |
| Object | fighter and interceptor aircraft |
—
|
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: fighter and interceptor aircraft | Statement: [Foxhound, natoNameCategory, fighter and interceptor aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natoNameCategory Context triple: [Foxhound, natoNameCategory, fighter and interceptor aircraft]
-
A.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
NATOname
Indicates that an entity has a specific official name as recognized or used by NATO.
-
C.
natoEquivalent
Indicates that one entity is the counterpart or functional equivalent of another within the NATO (North Atlantic Treaty Organization) framework.
-
D.
NATOCategory
chosen
Indicates that an entity is classified according to a specific NATO-defined category or designation.
-
E.
associatedWithNATO
Indicates a relationship in which an entity has a formal or recognized connection, affiliation, or involvement with NATO.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.