Triple
T27300807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiriwina Island |
E688901
|
entity |
| Predicate | hasMilitaryAirfieldDuring |
P159633
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [Kiriwina Island, hasMilitaryAirfieldDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryAirfieldDuring Context triple: [Kiriwina Island, hasMilitaryAirfieldDuring, World War II]
-
A.
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.
-
B.
airfieldUsedDuring
chosen
Indicates that an airfield was in operational use during a specified time period or event.
-
C.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
D.
hasTacticalAviationFacilities
Indicates that an entity possesses or hosts infrastructure and resources specifically designated for tactical aviation operations.
-
E.
airfieldEra
Indicates the historical time period or era during which an airfield was active, used, or relevant.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 11:21 a.m.