Triple
T29650828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 04/22 |
E750128
|
entity |
| Predicate | usedByAirport |
P18358
|
FINISHED |
| Object | Sultan Abdul Halim 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: Sultan Abdul Halim Airport | Statement: [Runway 04/22, usedByAirport, Sultan Abdul Halim Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAirport Context triple: [Runway 04/22, usedByAirport, Sultan Abdul Halim Airport]
-
A.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
B.
usesAirportCode
Indicates that one entity employs or identifies an airport by a specific standardized airport code.
-
C.
belongsToAirport
chosen
Indicates that one entity is part of, associated with, or under the jurisdiction of a specific airport.
-
D.
appliesToAirport
Indicates that something is relevant, valid, or specifically intended for use at a particular airport.
-
E.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 6:52 p.m.