Triple
T14999199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF 8x-xxxx |
E374037
|
entity |
| Predicate | identificationDomain |
P116293
|
FINISHED |
| Object | military 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: military aviation | Statement: [AF 8x-xxxx, identificationDomain, military aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identificationDomain Context triple: [AF 8x-xxxx, identificationDomain, military aviation]
-
A.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
identityConcept
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
-
D.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
E.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:54 a.m.