Triple
T7611835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver Leese |
E172257
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Leese |
E172257
|
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: Leese | Statement: [Oliver Leese, familyName, Leese]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leese Context triple: [Oliver Leese, familyName, Leese]
-
A.
Leese
chosen
Leese is an English surname most notably associated with British Army General Sir Oliver Leese, a senior commander during the Second World War.
-
B.
Kinsealy
Kinsealy is a suburban locality in north County Dublin, Ireland, known for its residential character and proximity to Swords and Dublin city.
-
C.
Tealing
Tealing is a small rural village in eastern Scotland, situated in the Angus council area just north of Dundee.
-
D.
Lundie
Lundie is a small rural settlement in Angus, Scotland, situated near the Sidlaw Hills and known for its scenic countryside setting.
-
E.
Lees
Lees is a village in the Metropolitan Borough of Oldham, Greater Manchester, England, historically part of Lancashire.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c868645f8081909439f63df3184628 |
completed | March 28, 2026, 11:46 p.m. |
Created at: March 27, 2026, 3:55 p.m.