Triple
T13383492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Burton |
E319376
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burton |
E62942
|
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: Burton | Statement: [Kate Burton, familyName, Burton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burton Context triple: [Kate Burton, familyName, Burton]
-
A.
Burton
chosen
Burton is the surname of acclaimed American filmmaker Tim Burton, known for his dark, gothic, and whimsical visual style.
-
B.
Burton
Burton is a masculine given name of English origin, notably borne by the American actor Burt Lancaster.
-
C.
Burton
Burton is a village and suburb situated just outside the coastal town of Christchurch in Dorset, England.
-
D.
Burch
Burch is a surname of English origin borne by various notable individuals across politics, arts, and other fields.
-
E.
Shadbolt
Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce80158819082156eaeaeda3bd8 |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7268cf04c8190a35fd48ce81c149e |
completed | May 3, 2026, 10:42 a.m. |
Created at: April 9, 2026, 9:33 p.m.