Triple
T35116280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air National Guard bases |
E1013445
|
entity |
| Predicate | mayShareFacilitiesWith |
P71121
|
FINISHED |
| Object | active duty United States Air Force bases |
—
|
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: active duty United States Air Force bases | Statement: [Air National Guard bases, mayShareFacilitiesWith, active duty United States Air Force bases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayShareFacilitiesWith Context triple: [Air National Guard bases, mayShareFacilitiesWith, active duty United States Air Force bases]
-
A.
sharesFacilityWith
chosen
Indicates that two entities use or have access to the same physical facility or location.
-
B.
haveSharedInfrastructure
Indicates that two or more entities use or depend on the same underlying physical or virtual infrastructure resources.
-
C.
allowsShares
Indicates that one entity grants another entity permission to share or distribute something.
-
D.
usesFacilityFor
Indicates that an entity makes use of a particular facility to carry out a specific purpose, activity, or function.
-
E.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.