Triple
T3089755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk |
E64456
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Falkenham |
E301442
|
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: Falkenham | Statement: [Suffolk, containsSettlement, Falkenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Falkenham Context triple: [Suffolk, containsSettlement, Falkenham]
-
A.
Falkenham
chosen
Falkenham is a small rural village and civil parish in Suffolk, England, situated near the River Deben in the East Suffolk district.
-
B.
Freckenham
Freckenham is a small rural village and civil parish located in the English county of Suffolk.
-
C.
Kentford
Kentford is a small village and civil parish in West Suffolk, England, situated near the border with Cambridgeshire.
-
D.
Laleham
Laleham is a riverside village in Surrey, England, situated on the River Thames and known for its historic church, green spaces, and residential character.
-
E.
Frittenden
Frittenden is a rural village and civil parish in the county of Kent in South East England, known for its historic church and traditional countryside character.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20d8f788190b05b8b6b5042bc1a |
completed | March 8, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f4dc9d481908b64d2d2bca0381a |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 8, 2026, 3:03 p.m.