Triple
T23784261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenland–Iceland–UK flyway |
E587906
|
entity |
| Predicate | hasWinteringAreasIn |
P97175
|
FINISHED |
| Object | British Isles |
—
|
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: British Isles | Statement: [Greenland–Iceland–UK flyway, hasWinteringAreasIn, British Isles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinteringAreasIn Context triple: [Greenland–Iceland–UK flyway, hasWinteringAreasIn, British Isles]
-
A.
winteringAreas
chosen
Indicates the locations where entities spend the winter season, typically as their non-breeding or overwintering grounds.
-
B.
lastRecordedWinteringLocation
Indicates the most recent location where an entity was known to spend the winter season.
-
C.
hasMigratoryBirdUse
Indicates that an entity is used, visited, or relied upon by migratory birds, such as for feeding, resting, or breeding during migration.
-
D.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
-
E.
hasBirdColony
Indicates that one entity hosts or contains a colony of birds associated with it.
- 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.