Triple
T5023455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Burke |
E112912
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burke |
E379595
|
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: Burke | Statement: [Thomas Burke, familyName, Burke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burke Context triple: [Thomas Burke, familyName, Burke]
-
A.
Burke
Burke is a town located in Dane County, Wisconsin, known as a suburban community near the city of Madison.
-
B.
Burke
chosen
Burke is a common Irish-origin surname borne by numerous notable figures across politics, the arts, and public life.
-
C.
Burke
Burke is a suburban community in Fairfax County, Northern Virginia, known for its residential neighborhoods, parks, and proximity to Washington, D.C.
-
D.
Edmund Burke
Edmund Burke was an 18th-century Irish statesman, political theorist, and philosopher widely regarded as the intellectual father of modern conservatism.
-
E.
Grenville
Grenville is a masculine given name most notably borne by American Civil War general and railroad engineer Grenville M. Dodge.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73670578819099a56112950708a8 |
completed | March 20, 2026, 4:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9286bb28819095ca0ec858061419 |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:36 p.m.