Triple
T16816538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Burtka |
E408765
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burtka |
E1073001
|
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: Burtka | Statement: [David Burtka, familyName, Burtka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burtka Context triple: [David Burtka, familyName, Burtka]
-
A.
Burtka
chosen
Burtka is a surname most prominently associated with American actor and chef David Burtka and his family.
-
B.
Sudylkiv
Sudylkiv is a village in Ukraine, historically part of the Russian Empire, known as the birthplace of Yiddish theater actor and director Maurice Schwartz.
-
C.
Buksa
Buksa is a Polish surname most notably borne by professional footballer Adam Buksa.
-
D.
Gabčík
Gabčík is a Slovak surname most notably borne by Jozef Gabčík, a World War II resistance fighter involved in the assassination of Nazi official Reinhard Heydrich.
-
E.
Bielke
Bielke is the surname of a notable Swedish noble family historically associated with prominent political and military figures.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e1de908190aa3508770fb865cf |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b297778c81909a2545c359739151 |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:23 a.m.