Triple
T10517944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCANDINAVIAN |
E248082
|
entity |
| Predicate | usedForIdentificationOf |
P9157
|
FINISHED |
| Object | Scandinavian Airlines flights |
—
|
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: Scandinavian Airlines flights | Statement: [SCANDINAVIAN, usedForIdentificationOf, Scandinavian Airlines flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForIdentificationOf Context triple: [SCANDINAVIAN, usedForIdentificationOf, Scandinavian Airlines flights]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
helpsIdentify
chosen
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
C.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
alternativeIdentification
Indicates that one entity serves as an alternative identifier or reference for another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.