Triple
T37851247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckley Field |
E944060
|
entity |
| Predicate | currentSiteUsedBy |
P16008
|
FINISHED |
| Object | United States Space Force |
—
|
NE NERFINISHED |
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: United States Space Force | Statement: [Buckley Field, currentSiteUsedBy, United States Space Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentSiteUsedBy Context triple: [Buckley Field, currentSiteUsedBy, United States Space Force]
-
A.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
B.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
C.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
D.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
E.
selectedAsSiteFor
Indicates that one entity has been chosen or designated to serve as the location or venue for another entity or activity.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:19 p.m.