Triple
T31043387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsley Field Air National Guard Base |
E791055
|
entity |
| Predicate | hasHostState |
P2928
|
FINISHED |
| Object | Oregon |
—
|
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: Oregon | Statement: [Kingsley Field Air National Guard Base, hasHostState, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostState Context triple: [Kingsley Field Air National Guard Base, hasHostState, Oregon]
-
A.
hostState
chosen
Indicates a relationship where one entity serves as the host or governing state for another entity, within whose jurisdiction, territory, or authority that other entity operates or resides.
-
B.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
C.
hasHosts
Indicates that one entity serves as the host or hosting environment for another entity.
-
D.
hasStateSystem
Indicates that an entity possesses, follows, or is governed by a particular system of state organization, rules, or governance.
-
E.
hasHostCharacter
Indicates that one entity serves as the host or primary character associated with another entity, such as a show, event, or media production.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 29, 2026, 8:59 p.m.