Triple
T6763462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Firth |
E154652
|
entity |
| Predicate | positionRelativeToOrkneyMainland |
P16235
|
FINISHED |
| Object | north coast |
—
|
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: north coast | Statement: [Bay of Firth, positionRelativeToOrkneyMainland, north coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToOrkneyMainland Context triple: [Bay of Firth, positionRelativeToOrkneyMainland, north coast]
-
A.
distanceToLerwickKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the town of Lerwick.
-
B.
distance to Tórshavn (kilometers)
Indicates the length, in kilometers, of the shortest travel distance between an entity and the location Tórshavn.
-
C.
positionRelativeToCoast
chosen
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
D.
distanceToOuterHebrides
Indicates the measured distance between a given entity’s location and the Outer Hebrides.
-
E.
distanceFromReykjavík
Indicates the spatial distance between an entity’s location and the city of Reykjavík.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.