Triple
T25592300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mattala Rajapaksa International Airport |
E641553
|
entity |
| Predicate | hubStatus |
P158879
|
FINISHED |
| Object | underutilized airport |
—
|
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: underutilized airport | Statement: [Mattala Rajapaksa International Airport, hubStatus, underutilized airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hubStatus Context triple: [Mattala Rajapaksa International Airport, hubStatus, underutilized airport]
-
A.
isBusyHub
Indicates that a location or node functions as a central point of activity with a high volume of interactions, traffic, or connections.
-
B.
platformStatus
Indicates the current operational or availability state of a platform within a system or service context.
-
C.
hostNationStatus
Indicates that an entity holds the official status of being the host nation for a particular event, activity, or arrangement.
-
D.
hubHeight
Indicates the vertical distance from the ground or reference level to the central hub point of a structure or device.
-
E.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
- F. None of above. chosen
Provenance (4 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96dd7dc8190a2d174239821d8bd |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:25 p.m.