Triple
T12613654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anmer |
E301193
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Anmer |
E301193
|
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: Anmer | Statement: [Anmer, civilParish, Anmer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anmer Context triple: [Anmer, civilParish, Anmer]
-
A.
Anmer
chosen
Anmer is a small rural village in Norfolk, England, notable for its proximity to the Sandringham Estate and its historic parish church.
-
B.
Smedvig
Smedvig is a Norwegian family name most prominently associated with the Smedvig shipping and oil services business dynasty.
-
C.
Bruinisse
Bruinisse is a fishing village and tourist destination in the Dutch province of Zeeland, known for its mussel industry and location on the Grevelingen.
-
D.
Denmead
Denmead is a large village and civil parish in Hampshire, England, situated near Waterlooville and on the edge of the South Downs.
-
E.
Ammer
The Ammer is a river in Bavaria, Germany, known for flowing through the Ammergau Alps and feeding the Ammersee.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d960c2e5b88190a7cc16002b218d8a |
completed | April 10, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ed1044c8190bbe881d32a4bf29e |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:12 p.m.