Triple
T9121504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietermaritzburg Airport |
E218860
|
entity |
| Predicate | supportsScheduledFlights |
P19814
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pietermaritzburg Airport, supportsScheduledFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScheduledFlights Context triple: [Pietermaritzburg Airport, supportsScheduledFlights, yes]
-
A.
hasScheduledFlights
chosen
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
B.
airSupportPlannedFrom
Indicates that air support operations are scheduled or intended to be provided starting from a specified source or location.
-
C.
supportsCommercialFlights
Indicates that the subject provides the necessary facilities, services, or conditions for regular commercial passenger or cargo flights to operate.
-
D.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
E.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b32ba88190b2b4406c7b905cca |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.