Triple
T5655931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottenby Nature Reserve |
E124617
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Ottenby village |
E519413
|
NE 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: Ottenby village | Statement: [Ottenby Nature Reserve, near, Ottenby village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ottenby village Context triple: [Ottenby Nature Reserve, near, Ottenby village]
-
A.
Ottenby
chosen
Ottenby is a nature reserve and historic estate at the southern tip of the Swedish island of Öland, known for its rich birdlife and coastal landscapes.
-
B.
Laceby
Laceby is a village and civil parish in North East Lincolnshire, England, situated near the town of Grimsby.
-
C.
Hallingby
Hallingby is a small village in the municipality of Ringerike in Buskerud county, Norway.
-
D.
Navenby
Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
-
E.
Barrowby
Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022fb0b74819084782411bd172834 |
completed | March 22, 2026, 5:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d9b43288190b6d7c610546b52f2 |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 3:42 p.m.