Triple
T20881652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Transat |
E514165
|
entity |
| Predicate | primaryDestinationsType |
P142230
|
FINISHED |
| Object | vacation 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: vacation destinations | Statement: [Air Transat, primaryDestinationsType, vacation destinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDestinationsType Context triple: [Air Transat, primaryDestinationsType, vacation destinations]
-
A.
primaryUSDestination
Indicates that an entity’s main or most significant destination within the United States is the specified location.
-
B.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
C.
primaryFreightDestination
Indicates the main location to which freight is intended to be shipped or delivered.
-
D.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
E.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67a33548190b0f5ba58b001d387 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:46 p.m.