Triple
T2038113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordwind Airlines |
E44678
|
entity |
| Predicate | targetDestinationType |
P30653
|
FINISHED |
| Object | holiday destinations |
—
|
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: holiday destinations | Statement: [Nordwind Airlines, targetDestinationType, holiday destinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDestinationType Context triple: [Nordwind Airlines, targetDestinationType, holiday destinations]
-
A.
servesDestinationType
chosen
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
B.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
C.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
D.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
E.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb95062c481908058d6da35337680 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.