Triple
T18683730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix–Mesa Gateway Airport |
E456799
|
entity |
| Predicate | primaryUseDuringMilitaryPeriod |
P30719
|
FINISHED |
| Object | pilot training |
—
|
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: pilot training | Statement: [Phoenix–Mesa Gateway Airport, primaryUseDuringMilitaryPeriod, pilot training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseDuringMilitaryPeriod Context triple: [Phoenix–Mesa Gateway Airport, primaryUseDuringMilitaryPeriod, pilot training]
-
A.
primaryUseLateWar
Indicates that something was used primarily during the later phase of a war, rather than in its early or middle stages.
-
B.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
D.
usedByDuringPeacetime
Indicates that one entity makes use of another specifically in contexts or periods classified as peacetime, rather than during war or conflict.
-
E.
wartimeUse
chosen
Indicates that something is used or employed during a period of war or armed conflict.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2abf3c8190958c03066b5814af |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.