Triple
T28376951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Peak Airfield |
E718778
|
entity |
| Predicate | rethemedAsGrizzlyPeakAirfield |
P165441
|
FINISHED |
| Object | 2015-05-15 |
—
|
LITERAL FINISHED |
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: 2015-05-15 | Statement: [Grizzly Peak Airfield, rethemedAsGrizzlyPeakAirfield, 2015-05-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rethemedAsGrizzlyPeakAirfield Context triple: [Grizzly Peak Airfield, rethemedAsGrizzlyPeakAirfield, 2015-05-15]
-
A.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
B.
hasFormerMilitaryAirfield
Indicates that an entity possesses or is associated with an airfield that was previously used for military purposes but is no longer active as such.
-
C.
airfieldUsedDuring
Indicates that an airfield was in operational use during a specified time period or event.
-
D.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
-
E.
airfieldOpened
Indicates that an airfield began operations or was officially opened at a certain time.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 1:03 a.m.