Triple
T31043388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsley Field Air National Guard Base |
E791055
|
entity |
| Predicate | hasGuardUnit |
P170692
|
FINISHED |
| Object | Oregon Air National Guard 173rd Fighter Wing |
—
|
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 Air National Guard 173rd Fighter Wing | Statement: [Kingsley Field Air National Guard Base, hasGuardUnit, Oregon Air National Guard 173rd Fighter Wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuardUnit Context triple: [Kingsley Field Air National Guard Base, hasGuardUnit, Oregon Air National Guard 173rd Fighter Wing]
-
A.
hasGuardCharacter
Indicates that one entity serves as a guard or protective character for another entity.
-
B.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
C.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
D.
hasGuardBars
Indicates that one entity is equipped with or protected by guard bars installed on or around it.
-
E.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f694fb85f881909734cf13cea84c78 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 8:59 p.m.