Triple
T3089602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk |
E64456
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Horringer |
E299774
|
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: Horringer | Statement: [Suffolk, containsSettlement, Horringer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horringer Context triple: [Suffolk, containsSettlement, Horringer]
-
A.
Horringer
chosen
Horringer is a village and civil parish in Suffolk, England, known for its rural character and proximity to the town of Bury St Edmunds.
-
B.
Hannington
Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
-
C.
Harrodstown
Harrodstown was the original pioneer settlement that later became Harrodsburg, recognized as one of the earliest permanent European-American communities in Kentucky.
-
D.
Harrold
Harrold is a given name and surname, used as a variant spelling of Harold.
-
E.
Halstead
Halstead is a historic market town in the county of Essex in the East of England.
- 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_69b1f8a4c1f08190a80efd190e4ed07f |
completed | March 11, 2026, 11:20 p.m. |
Created at: March 8, 2026, 3:03 p.m.