Triple
T6213239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otis Air Force Base |
E138920
|
entity |
| Predicate | closedAsActiveDutyUSAFBase |
P61288
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [Otis Air Force Base, closedAsActiveDutyUSAFBase, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsActiveDutyUSAFBase Context triple: [Otis Air Force Base, closedAsActiveDutyUSAFBase, 1973]
-
A.
closedAsActiveArmyPost
Indicates that a location or facility ceased operations specifically in its role as an active Army post.
-
B.
airfieldDecommissioned
chosen
Indicates that an airfield has been officially taken out of service and is no longer used for regular aviation operations.
-
C.
militaryBasis
Indicates that one entity serves as the foundational military justification, rationale, or underlying military reason for another entity or action.
-
D.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
wasMilitaryBaseDuring
Indicates that a location functioned as a military base during a specified time period or event.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0628c52ec8190b9c62c7fdc0aa83b |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.