Triple
T19673946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savile |
E472404
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Saville |
—
|
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: Saville | Statement: [Savile, hasVariant, Saville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saville Context triple: [Savile, hasVariant, Saville]
-
A.
Savile
chosen
Savile is an English surname historically associated with several notable figures in British political, academic, and social life.
-
B.
Lindley
Lindley is the surname of American actor and rodeo performer Slim Pickens, born Louis Burton Lindley Jr.
-
C.
Lindley
Lindley refers to John Lindley, a prominent 19th-century English botanist known for his influential work in plant taxonomy and classification.
-
D.
Neave
Neave is a surname most notably associated with Airey Neave, a British Conservative politician and war hero involved in World War II and postwar politics.
-
E.
Challis
Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416e19d881909248c4f778f7147a |
completed | April 20, 2026, 3:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.