Triple
T33652186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skytrax Airline of the Year 2001 |
E862126
|
entity |
| Predicate | organizerSpecialization |
P113517
|
FINISHED |
| Object | airline ratings |
—
|
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: airline ratings | Statement: [Skytrax Airline of the Year 2001, organizerSpecialization, airline ratings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizerSpecialization Context triple: [Skytrax Airline of the Year 2001, organizerSpecialization, airline ratings]
-
A.
organizerRepresents
Indicates that an organizer acts on behalf of, or serves as the representative of, another entity in a given context.
-
B.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
C.
organizerBase
Indicates that one entity serves as the primary or foundational organizer for another entity or event.
-
D.
organizerIndustry
chosen
Indicates the industry or business sector in which the organizer operates or is classified.
-
E.
organizers
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:42 a.m.