Triple
T13754442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibton Abbey |
E330437
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Sibton |
E330437
|
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: Sibton | Statement: [Sibton Abbey, locatedIn, Sibton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sibton Context triple: [Sibton Abbey, locatedIn, Sibton]
-
A.
Sibton
chosen
Sibton is a small rural village and civil parish located in the English county of Suffolk.
-
B.
Buntingford
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
C.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
D.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
-
E.
Birkett
Birkett is a well-known hillwalking guidebook and classification list of Lake District fells compiled by Bill Birkett.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02179c948190a652cc8c586e418f |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a85813e88190a63fecf8b0675df6 |
completed | May 3, 2026, 7:56 p.m. |
Created at: April 9, 2026, 10:09 p.m.