Triple
T24218249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Iceland Connect |
E601365
|
entity |
| Predicate | internationalDestination |
P54353
|
FINISHED |
| Object | Nuuk |
—
|
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: Nuuk | Statement: [Air Iceland Connect, internationalDestination, Nuuk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalDestination Context triple: [Air Iceland Connect, internationalDestination, Nuuk]
-
A.
internationalDestinationsInclude
chosen
Indicates that a given entity’s set of international destinations contains or covers the specified destination(s).
-
B.
travelsAbroad
Indicates that an entity goes to or spends time in a foreign country outside its usual nation of residence.
-
C.
travelZone
Indicates a relationship where an entity is located in, moves within, or is permitted to move within a specified geographic or regulatory area.
-
D.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
E.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820a80ec8190bd11f08f7733843d |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:58 p.m.