Triple
T8441347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Leitch |
E199357
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Leitch |
E159441
|
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: Leitch | Statement: [David Leitch, familyName, Leitch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leitch Context triple: [David Leitch, familyName, Leitch]
-
A.
Leitch
chosen
Leitch is a Scottish surname most notably associated with Archibald Leitch, a pioneering early 20th-century football stadium architect.
-
B.
Gillen
Gillen is a small coastal settlement on the Waternish peninsula of the Isle of Skye in Scotland.
-
C.
Laird
Laird is a given name of Scottish origin traditionally used as a masculine middle or first name, associated with landownership and nobility.
-
D.
Savini
Savini is an Italian surname most famously associated with Tom Savini, a renowned special effects and makeup artist in horror cinema.
-
E.
Flecher
Flecher is a variant spelling of the surname Fletcher, which traditionally refers to a maker or seller of arrows.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe138a94081908e306d22aaa39b24 |
completed | March 31, 2026, 2:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1d9ab3a88190ada7741cf054fc1b |
completed | April 2, 2026, 7:41 a.m. |
Created at: March 30, 2026, 6:08 p.m.