Triple
T33652930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAS flights |
E862147
|
entity |
| Predicate | flagCarrierFor |
P177474
|
FINISHED |
| Object | Denmark |
—
|
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: Denmark | Statement: [SAS flights, flagCarrierFor, Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagCarrierFor Context triple: [SAS flights, flagCarrierFor, Denmark]
-
A.
flagCarrierProgramOf
Indicates that an airline serves as the designated national flag carrier within a specific airline loyalty or program context.
-
B.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
-
C.
flagshipAt
Indicates that a particular entity serves as the primary or leading representative (flagship) of something at or for a specified location, organization, or context.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
E.
flagBearer
Indicates that one entity serves as the carrier or holder of a flag on behalf of another entity, group, or cause.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:42 a.m.