Triple
T5222614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentish ragstone |
E117906
|
entity |
| Predicate | quarriedIn |
P3992
|
FINISHED |
| Object | Ditton |
E338764
|
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: Ditton | Statement: [Kentish ragstone, quarriedIn, Ditton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ditton Context triple: [Kentish ragstone, quarriedIn, Ditton]
-
A.
Ditton
chosen
Ditton is a village and civil parish in Kent, England, situated within the Tonbridge and Malling district.
-
B.
Tadlow
Tadlow is a small rural village in the county of Cambridgeshire in eastern England, known for its historic church and agricultural surroundings.
-
C.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
D.
Botesdale
Botesdale is a small rural village in Suffolk, England, known for its historic buildings and traditional village character.
-
E.
Denston
Denston is a small rural village and civil parish located in the county of Suffolk in eastern 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abba82881908c030ba55146b8ea |
completed | March 20, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beeff852bc81908467a343c5ded404 |
completed | March 21, 2026, 7:22 p.m. |
Created at: March 20, 2026, 1:48 p.m.