Triple
T13234536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire coalfield |
E315109
|
entity |
| Predicate | majorMiningTowns |
P105974
|
FINISHED |
| Object | Armthorpe |
E684159
|
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: Armthorpe | Statement: [Yorkshire coalfield, majorMiningTowns, Armthorpe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Armthorpe Context triple: [Yorkshire coalfield, majorMiningTowns, Armthorpe]
-
A.
Armthorpe
chosen
Armthorpe is a village and civil parish in South Yorkshire, England, situated near Doncaster and known historically for its coal mining community.
-
B.
Gunthorpe
Gunthorpe is a village in Nottinghamshire, England, situated on the River Trent and known for its riverside setting and transport links.
-
C.
Stragglethorpe
Stragglethorpe is a small English village situated in rural Lincolnshire, known for its agricultural surroundings and historic character.
-
D.
Harpenden
Harpenden is a commuter town in southern England known for its green spaces and affluent residential character.
-
E.
Apethorpe
Apethorpe is a village in Northamptonshire, England, known for its historic country house and rural character.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f71c5388190a6e122e14384efd7 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff2dca2c81909cab1aa868ad575d |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:22 p.m.