Triple
T16581426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botulph |
E402839
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Thorney |
E408010
|
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: Thorney | Statement: [Botulph, associatedWith, Thorney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thorney Context triple: [Botulph, associatedWith, Thorney]
-
A.
Thorney
chosen
Thorney is a village in Cambridgeshire, England, historically centered around its important medieval Benedictine abbey.
-
B.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
-
C.
Dorchester-on-Thames
Dorchester-on-Thames is a historic English village in Oxfordshire known for its medieval abbey and picturesque setting at the confluence of the River Thames and River Thame.
-
D.
Thurne
Thurne is a small village in Norfolk, England, known for its location within the Norfolk Broads and its iconic Thurne windpump.
-
E.
Thorne
Thorne is a small market town in South Yorkshire, England, known for its historic waterways, including canals and navigable rivers.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35998371c8190936dcdaab5ca7e21 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ef0bc4c8190b06b03c06d344abf |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:16 a.m.