Triple
T18586305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Burnside |
E454243
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burnside |
—
|
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: Burnside | Statement: [John Burnside, familyName, Burnside]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burnside Context triple: [John Burnside, familyName, Burnside]
-
A.
Burnside
chosen
Burnside is a surname of English and Scottish origin borne by various notable individuals, including Australian barrister and human rights advocate Julian Burnside.
-
B.
Burnside
Burnside is a suburban residential area in South Lanarkshire, Scotland, situated on the outskirts of Glasgow near the town of Rutherglen.
-
C.
Burnside
Burnside is a locality in Queensland, Australia, situated near the rural area of Perwillowen on the Sunshine Coast.
-
D.
Burnside’s Bridge
Burnside’s Bridge is a historic stone arch bridge at Antietam National Battlefield in Maryland, best known as the focal point of intense fighting during the Battle of Antietam in the American Civil War.
-
E.
Sherman
Sherman is a city in north-central Texas that serves as a regional hub for commerce and transportation in the Texoma area.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b210488190ba62d3bf6e1a595c |
completed | April 19, 2026, 9:14 p.m. |
Created at: April 10, 2026, 11:44 a.m.