Triple
T6893909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KAL |
E159120
|
entity |
| Predicate | associatedAirlineServiceType |
P73990
|
FINISHED |
| Object | passenger transport |
—
|
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: passenger transport | Statement: [KAL, associatedAirlineServiceType, passenger transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirlineServiceType Context triple: [KAL, associatedAirlineServiceType, passenger transport]
-
A.
associatedAirlineGroup
Indicates a relationship where an airline is linked or belongs to a specific airline group or alliance.
-
B.
associatedAirlineICAOCode
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
-
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.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
E.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline code.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d931da24819096b9b205f2c0ebb0 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.