Triple
T9959213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Aviation Forces of Spain |
E195522
|
entity |
| Predicate | typeOfAviation |
P91661
|
FINISHED |
| Object | battlefield aviation |
—
|
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: battlefield aviation | Statement: [Army Aviation Forces of Spain, typeOfAviation, battlefield aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAviation Context triple: [Army Aviation Forces of Spain, typeOfAviation, battlefield aviation]
-
A.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
typicalAircraftTypeCategory
Indicates the general class or category of aircraft type that is most commonly associated with or used in a given context.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
planeCategory
Indicates the classification or type of a plane within a defined categorization scheme.
-
E.
isAviationElementFor
Indicates that something serves as an aviation-related component, feature, or element specifically associated with or used for a particular object, system, or context.
- F. None of above. chosen
Provenance (4 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d08fdc8190a77b9c97830035bc |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:46 p.m.