Triple
T3030043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nambour |
E82871
|
entity |
| Predicate | nearbyLocality |
P4647
|
FINISHED |
| Object | Burnside |
E117608
|
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: Burnside | Statement: [Nambour, nearbyLocality, Burnside]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burnside Context triple: [Nambour, nearbyLocality, 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.
Sherman
Sherman is a city in north-central Texas that serves as a regional hub for commerce and transportation in the Texoma area.
-
C.
Burnside Bridge
Burnside Bridge is a historic bascule bridge over the Willamette River in Portland, Oregon, carrying one of the city’s major east–west thoroughfares.
-
D.
Burnside Bridge
Burnside Bridge is a historic stone arch bridge in Maryland best known as a focal point of intense fighting during the American Civil War’s Battle of Antietam.
-
E.
Macdonough
Macdonough is a surname most notably associated with Thomas Macdonough, a distinguished early 19th-century U.S. naval officer and War of 1812 hero.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aecd384819085d15f701add7c44 |
completed | March 8, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1deb9c9548190b3d36803432b84f6 |
completed | March 11, 2026, 9:29 p.m. |
Created at: March 8, 2026, 3:01 p.m.