Triple
T6160041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Two |
E137416
|
entity |
| Predicate | followsNamingConvention |
P1217
|
FINISHED |
| Object | "Air Force" + numerical designator |
—
|
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: "Air Force" + numerical designator | Statement: [Air Force Two, followsNamingConvention, "Air Force" + numerical designator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNamingConvention Context triple: [Air Force Two, followsNamingConvention, "Air Force" + numerical designator]
-
A.
followsNameOf
Indicates that one entity’s name comes immediately after another entity’s name in a specified ordering or sequence.
-
B.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
C.
isArbitraryConvention
Indicates that the relationship or rule exists due to social or contextual agreement rather than inherent necessity or natural law.
-
D.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3445dc8190822954cee90f0dd7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.