Triple
T3541795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lees Urban District |
E74901
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Lees |
E367416
|
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: Lees | Statement: [Lees Urban District, containsSettlement, Lees]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lees Context triple: [Lees Urban District, containsSettlement, Lees]
-
A.
Lees
chosen
Lees is a village in the Metropolitan Borough of Oldham, Greater Manchester, England, historically part of Lancashire.
-
B.
Leer
Leer is a historic town in northwestern Germany known for its maritime heritage and traditional East Frisian culture.
-
C.
Leens
Leens is a village in the Dutch province of Groningen, located within the municipality of Het Hogeland.
-
D.
Leese
Leese is an English surname most notably associated with British Army General Sir Oliver Leese, a senior commander during the Second World War.
-
E.
Lessi
Lessi is a diminutive or affectionate nickname commonly used for the Italian given name Alessandro.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf73c5e881909a8352512928377b |
completed | March 8, 2026, 6:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3bb8b7fac81908c18d3f868aeba44 |
completed | March 13, 2026, 7:23 a.m. |
Created at: March 8, 2026, 3:20 p.m.