Triple
T14169521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewart Air National Guard Base |
E351168
|
entity |
| Predicate | openedToMilitaryUse |
P7893
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [Stewart Air National Guard Base, openedToMilitaryUse, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToMilitaryUse Context triple: [Stewart Air National Guard Base, openedToMilitaryUse, World War II era]
-
A.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
B.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
C.
openedToMilitaryTraffic
Indicates that a route, facility, or passage has been made accessible and available for use by military vehicles or operations.
-
D.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
E.
openedAsMilitaryAirfield
chosen
Indicates that an airfield was originally established and began operation specifically for military aviation use.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.