Triple
T25812279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIJJ |
E650143
|
entity |
| Predicate | linkedAirportName |
P16112
|
FINISHED |
| Object | Adisutjipto International Airport |
—
|
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: Adisutjipto International Airport | Statement: [WIJJ, linkedAirportName, Adisutjipto International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedAirportName Context triple: [WIJJ, linkedAirportName, Adisutjipto International Airport]
-
A.
airportLinkName
Indicates the name assigned to a transportation link or connection associated with an airport.
-
B.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
C.
associatedAirportLocalName
Indicates the local or native-language name of the airport that is associated with the given entity.
-
D.
associatedWithAirportName
chosen
Indicates a relationship where an entity is linked or connected to a specific airport by its name.
-
E.
associatedHubAirport
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
- 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_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 22, 2026, 7:11 a.m.