Triple
T37962385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sioux Gateway Airport |
E947039
|
entity |
| Predicate | formerMilitaryName |
P203134
|
FINISHED |
| Object | Sioux City Army Air Base |
—
|
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: Sioux City Army Air Base | Statement: [Sioux Gateway Airport, formerMilitaryName, Sioux City Army Air Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMilitaryName Context triple: [Sioux Gateway Airport, formerMilitaryName, Sioux City Army Air Base]
-
A.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
B.
postMilitaryName
Indicates the name or designation an entity holds after completing or leaving military service.
-
C.
militaryBranchPredecessorOf
Indicates that one military branch served as the organizational or historical predecessor to another military branch.
-
D.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
E.
militaryBranchAbbreviation
Indicates the standard shortened form or acronym used to represent a specific branch of a military organization.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
| PDg | Predicate description generation | batch_6a012593db3c8190b339c4db93f87e89 |
completed | May 11, 2026, 12:40 a.m. |
Created at: May 3, 2026, 4:20 p.m.