Triple
T34484994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SilkAir |
E885291
|
entity |
| Predicate | inFlightClasses |
P120765
|
FINISHED |
| Object | Business Class |
—
|
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: Business Class | Statement: [SilkAir, inFlightClasses, Business Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inFlightClasses Context triple: [SilkAir, inFlightClasses, Business Class]
-
A.
inFlightService
Indicates that a service or activity is being provided to passengers during a flight.
-
B.
airlineClass
chosen
Indicates the specific travel class or service level assigned to a passenger or ticket on an airline flight.
-
C.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
-
D.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
E.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.