Triple
T10857164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irwell Valley |
E256296
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kearsley |
E159246
|
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: Kearsley | Statement: [Irwell Valley, contains, Kearsley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kearsley Context triple: [Irwell Valley, contains, Kearsley]
-
A.
Kearsley
chosen
Kearsley is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
B.
Torresdale
Torresdale is a residential neighborhood in the far northeastern section of Philadelphia, Pennsylvania, known for its proximity to the Delaware River and suburban character.
-
C.
Knaphill
Knaphill is a suburban village in Surrey, England, forming part of the borough of Woking.
-
D.
Banwell
Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
-
E.
Styal
Styal is a village in Cheshire, England, known for its historic cotton mill and role in the early Industrial Revolution.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb197808c8190b1c80aeb2144a909 |
completed | April 14, 2026, 9:28 p.m. |
Created at: April 8, 2026, 9:20 p.m.