Triple
T25812234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maguwo Airfield |
E650142
|
entity |
| Predicate | originalAirportFor |
P81616
|
FINISHED |
| Object | Yogyakarta |
—
|
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: Yogyakarta | Statement: [Maguwo Airfield, originalAirportFor, Yogyakarta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalAirportFor Context triple: [Maguwo Airfield, originalAirportFor, Yogyakarta]
-
A.
originAirportHub
Indicates that the referenced airport serves as a primary hub or main operating base for the associated airline or carrier.
-
B.
originAirportICAO
Indicates the airport, identified by its ICAO code, from which a flight or journey departs.
-
C.
originAirportWhenMissing
Indicates the airport that should be treated as the origin when the actual origin airport information is missing.
-
D.
previousPrimaryAirportFor
chosen
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
-
E.
hasOriginAirport
Indicates that something, typically a flight or journey, departs from or is associated with a specific origin airport.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 22, 2026, 7:11 a.m.