Triple
T25812280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIJJ |
E650143
|
entity |
| Predicate | linkedAirportMilitaryUse |
P34628
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WIJJ, linkedAirportMilitaryUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedAirportMilitaryUse Context triple: [WIJJ, linkedAirportMilitaryUse, yes]
-
A.
airportServesMilitaryTraffic
chosen
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
-
B.
usedByMilitaryInstallations
Indicates that something is utilized or operated by military installations for their functions or activities.
-
C.
relatedAirfield
Indicates that there is an association or connection between an entity and a specific airfield, such as operational use, location, or administrative linkage.
-
D.
hasTacticalAviationFacilities
Indicates that an entity possesses or hosts infrastructure and resources specifically designated for tactical aviation operations.
-
E.
operatesAirbasesIn
Indicates that an entity manages, controls, or conducts operations at airbases located within a specified area or jurisdiction.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 22, 2026, 7:11 a.m.