Triple
T23784262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenland–Iceland–UK flyway |
E587906
|
entity |
| Predicate | hasStopoverSiteIn |
P87960
|
FINISHED |
| Object | Iceland |
—
|
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: Iceland | Statement: [Greenland–Iceland–UK flyway, hasStopoverSiteIn, Iceland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStopoverSiteIn Context triple: [Greenland–Iceland–UK flyway, hasStopoverSiteIn, Iceland]
-
A.
isStopoverSiteFor
Indicates that a location serves as a temporary stopping or resting point along the route or journey of another entity.
-
B.
hasStopoverState
Indicates that an entity’s journey or process includes an intermediate stop or temporary state before reaching its final destination or outcome.
-
C.
hasStops
Indicates that a route, service, or journey includes one or more intermediate stopping points at specified locations.
-
D.
stopoverLocation
Indicates that an entity makes an intermediate stop or layover at a specified location during a journey or route.
-
E.
stopoverCountry
chosen
Indicates that a journey or flight includes an intermediate stop in a specified country before reaching its final destination.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62f8d2881908a1fe153cfaaacbc |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:17 p.m.