Triple
T795496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L. S. Lowry |
E17010
|
entity |
| Predicate | workLocation |
P7
|
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: [L. S. Lowry, workLocation, Pendlebury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pendlebury Context triple: [L. S. Lowry, workLocation, 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.
Bredbury
Bredbury is a suburban town in Greater Manchester, England, situated near Stockport and known for its residential character and local industrial heritage.
-
C.
Hordley
Hordley is a small rural settlement located in the parish of St. Thomas in the East, Jamaica.
-
D.
Ribblehead
Ribblehead is a remote hamlet in North Yorkshire, England, best known for its dramatic moorland setting and the iconic Ribblehead Viaduct on the Settle–Carlisle railway.
-
E.
Narborough
Narborough is a village in the English county of Norfolk, known for its rural setting and historic parish 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b04cd8819092e2fd7ba4df8672 |
completed | March 1, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7a3b1a81481908c831d1f43b9d014 |
completed | March 4, 2026, 3:14 a.m. |
Created at: March 1, 2026, 7:38 p.m.