Triple
T5812794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arun District |
E128909
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object | Angmering |
E143263
|
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: Angmering | Statement: [Arun District, hasParish, Angmering]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Angmering Context triple: [Arun District, hasParish, Angmering]
-
A.
Angmering
chosen
Angmering is a large village and civil parish in the Arun district of West Sussex, England, situated between Littlehampton and Worthing near the south coast.
-
B.
Bermaringen
Bermaringen is a village and district within the municipality of Blaustein in the Alb-Donau region of Baden-Württemberg, Germany.
-
C.
Kessingland
Kessingland is a coastal village and civil parish in Suffolk, England, known for its long shingle beach and seaside tourism.
-
D.
Wilhering
Wilhering is a municipality in Upper Austria, known for the historic Wilhering Abbey and its location near the city of Linz.
-
E.
Flumenthal
Flumenthal is a municipality in the canton of Solothurn in northwestern Switzerland.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b56044c8190847478a342d441c2 |
completed | March 22, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a1826cc081909572d9bf99d5f670 |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:52 p.m.