Triple
T30411825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Abdul Aziz Shah Airport |
E773639
|
entity |
| Predicate | primaryAirportForRegion |
P75084
|
FINISHED |
| Object | domestic flights |
—
|
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: domestic flights | Statement: [Sultan Abdul Aziz Shah Airport, primaryAirportForRegion, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAirportForRegion Context triple: [Sultan Abdul Aziz Shah Airport, primaryAirportForRegion, domestic flights]
-
A.
isMajorRegionalAirportFor
chosen
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
B.
otherMajorAirportInRegion
Indicates that the subject airport is a different major airport located within the same geographic region as the object airport.
-
C.
previousPrimaryAirportFor
Indicates that one airport was formerly the main or primary airport serving a particular location or entity before being replaced by another.
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a021f84715881908e25b6548e7cf62e |
completed | May 11, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_6a021739b7288190a4ca94c04074c78a |
completed | May 11, 2026, 5:51 p.m. |
Created at: April 29, 2026, 8:05 p.m.