Triple
T3119307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agecroft Colliery |
E65141
|
entity |
| Predicate | employerIn |
P33603
|
FINISHED |
| Object | Pendlebury |
E10842
|
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: Pendlebury | Statement: [Agecroft Colliery, employerIn, Pendlebury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pendlebury Context triple: [Agecroft Colliery, employerIn, Pendlebury]
-
A.
Pendlebury
chosen
Pendlebury is a suburban area in the City of Salford, Greater Manchester, England, historically known for its coal mining and textile industries.
-
B.
Pilton
Pilton is a residential district in the north of Edinburgh, Scotland, known for its large housing estates and proximity to Granton.
-
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.
Bredbury
Bredbury is a suburban town in Greater Manchester, England, situated near Stockport and known for its residential character and local industrial heritage.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e975f08190a91a01f37a31b766 |
completed | March 8, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b261f21620819088b6e7f782efe0b8 |
completed | March 12, 2026, 6:49 a.m. |
Created at: March 8, 2026, 3:04 p.m.