Triple
T34513871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whenuapai Airport |
E886094
|
entity |
| Predicate | primaryUseAfter1965 |
P69258
|
FINISHED |
| Object | military operations |
—
|
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: military operations | Statement: [Whenuapai Airport, primaryUseAfter1965, military operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseAfter1965 Context triple: [Whenuapai Airport, primaryUseAfter1965, military operations]
-
A.
ownerAfter1964
Indicates that an entity became the owner of something at some point after the year 1964.
-
B.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
C.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
D.
laterPrimarilyUsedFor
chosen
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
-
E.
statusAfter1965
Indicates the status or condition of an entity as it exists at any time after the year 1965.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.