Triple
T36168558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Air Station Olathe |
E1046080
|
entity |
| Predicate | hasNameAfterClosure |
P189817
|
FINISHED |
| Object | New Century AirCenter |
—
|
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: New Century AirCenter | Statement: [Naval Air Station Olathe, hasNameAfterClosure, New Century AirCenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameAfterClosure Context triple: [Naval Air Station Olathe, hasNameAfterClosure, New Century AirCenter]
-
A.
postClosureName
chosen
Indicates the name assigned to something after a closure event or process has occurred.
-
B.
hasClosure
Indicates that one entity possesses, defines, or is associated with the closure (completion or boundary-encompassing form) of another entity or operation.
-
C.
hasOpeningNamedAfter
Indicates that an opening (such as in a game, work, or structure) is named after a particular entity.
-
D.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
E.
namedAfterCall
Indicates that one entity is named after another entity as a result of a specific call or naming action.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:08 p.m.