Triple
T20772288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leigh Leopards |
E511265
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Leigh, Greater Manchester, England |
—
|
NE NERFINISHED |
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: Leigh, Greater Manchester, England | Statement: [Leigh Leopards, location, Leigh, Greater Manchester, England]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leigh, Greater Manchester, England Context triple: [Leigh Leopards, location, Leigh, Greater Manchester, England]
-
A.
Leigh
Leigh is a given name and surname of English origin, used for all genders and often considered a variant spelling of "Lee."
-
B.
Leigh
Leigh is a village and civil parish in the Malvern Hills district of Worcestershire, England.
-
C.
Leigh
chosen
Leigh is a parliamentary constituency in Greater Manchester, England, historically represented in the UK House of Commons.
-
D.
Leigh
Leigh is a small coastal town in the Auckland Region of New Zealand known as a gateway to popular marine and coastal attractions.
-
E.
Egremont, Lancashire, England
Egremont, Lancashire, England is a small village in the North West of England, historically part of the county of Lancashire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2681ff88190bfe5938c2db6b2c4 |
completed | April 21, 2026, 12:18 a.m. |
Created at: April 16, 2026, 12:37 p.m.