Triple
T13691242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finningham |
E328267
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Finningham |
E328267
|
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: Finningham | Statement: [Finningham, civilParish, Finningham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Finningham Context triple: [Finningham, civilParish, Finningham]
-
A.
Finningham
chosen
Finningham is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
B.
Fakenham
Fakenham is a market town in Norfolk, England, known historically for its agriculture and as a local commercial center.
-
C.
Swaffham
Swaffham is a historic market town in the English county of Norfolk, known for its traditional town center and surrounding rural landscape.
-
D.
Swaffham Bulbeck
Swaffham Bulbeck is a rural village and civil parish in Cambridgeshire, England, known for its historic church, traditional architecture, and agricultural surroundings.
-
E.
Gressingham
Gressingham is a small rural village in Lancashire, England, known for its picturesque setting near the River Lune.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8746458819095ec1ba3c01ef31b |
completed | April 12, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a8416d808190bd9cb77e0dd0d4be |
completed | May 3, 2026, 7:55 p.m. |
Created at: April 9, 2026, 9:53 p.m.