Triple
T18515185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Peake |
E452440
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Peake |
E1202740
|
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: Peake | Statement: [Bill Peake, familyName, Peake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peake Context triple: [Bill Peake, familyName, Peake]
-
A.
Peake
chosen
Peake is a surname most notably associated with British astronaut Tim Peake, the first official UK astronaut to visit the International Space Station.
-
B.
Paice
Paice is the surname of Ian Paice, the renowned English drummer best known as a founding member of the rock band Deep Purple.
-
C.
Pearce
Pearce is a surname and given name of English origin, commonly considered a variant of "Pierce" and ultimately derived from the name "Peter."
-
D.
Pearce
Pearce is an Australian federal electoral division in Western Australia, represented in the House of Representatives.
-
E.
McGwyre
McGwyre is a variant spelling of the surname Maguire, an Irish family name of Gaelic origin.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53349415c8190b989b536e2d1c40a |
completed | April 19, 2026, 7:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a04916c1cb88190889ad7d1c1dc4279 |
completed | May 13, 2026, 2:57 p.m. |
Created at: April 10, 2026, 11:36 a.m.