Triple
T26905441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExpressTram |
E677238
|
entity |
| Predicate | primaryAirlineServed |
P12356
|
FINISHED |
| Object | Delta Air Lines |
—
|
NE NERFINISHED |
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: Delta Air Lines | Statement: [ExpressTram, primaryAirlineServed, Delta Air Lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAirlineServed Context triple: [ExpressTram, primaryAirlineServed, Delta Air Lines]
-
A.
primaryHubAirline
Indicates that an airline serves as the main or principal hub carrier for a particular airport or location.
-
B.
servesAirline
chosen
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.
primaryAirlinePartner
Indicates that one airline serves as the main or preferred partner airline for another entity, such as a traveler, company, or loyalty program.
-
E.
airlineUsed
Indicates that a particular airline is employed or chosen for transporting someone or something in a given trip or flight.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 27, 2026, 5:58 a.m.