Triple
T36230440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Cooke, California |
E891225
|
entity |
| Predicate | successorFacilityOperatedBy |
P105832
|
FINISHED |
| Object | United States Air 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 Air Force | Statement: [Camp Cooke, California, successorFacilityOperatedBy, United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorFacilityOperatedBy Context triple: [Camp Cooke, California, successorFacilityOperatedBy, United States Air Force]
-
A.
facilityOperatedBy
chosen
Indicates that a facility is managed, run, or controlled by a specified agent or organization.
-
B.
successorFacility
Indicates that one facility directly follows and replaces another in function, ownership, or operation.
-
C.
formerlyOperatedBy
Indicates that an entity was previously operated or managed by another entity, but is no longer under that operation.
-
D.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
E.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 3, 2026, 4:09 p.m.