Triple
T689700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SriLankan Airlines |
E13363
|
entity |
| Predicate | offersCodeShareFlights |
P10967
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SriLankan Airlines, offersCodeShareFlights, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersCodeShareFlights Context triple: [SriLankan Airlines, offersCodeShareFlights, true]
-
A.
hasCodeShareOrInterline
chosen
Indicates that there exists a codeshare or interline agreement relationship between the referenced transportation services or carriers.
-
B.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
C.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
D.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline code.
-
E.
hasUnderlyingAirlineCallsign
Indicates that an airline-related entity is associated with a specific underlying airline callsign used for identification in air traffic communications.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0ad379c81909003d35c63822780 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.