Triple
T8824903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SG postcode area |
E209989
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Buntingford |
E196449
|
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: Buntingford | Statement: [SG postcode area, hasPostTown, Buntingford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buntingford Context triple: [SG postcode area, hasPostTown, Buntingford]
-
A.
Buntingford
chosen
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
B.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
C.
Buckland
Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
-
D.
Buckland
Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
-
E.
Buckland
Buckland is a residential suburb located on Portsea Island within the city of Portsmouth on England’s south coast.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc603220508190b64e22dec3ee5ceb |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa060ccd0819082824c8595b244a6 |
completed | April 3, 2026, 11:11 a.m. |
Created at: March 30, 2026, 6:46 p.m.