Triple
T9405671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadzio |
E226579
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Tadzio (diminutive of Tadeusz) |
E225535
|
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: Tadzio (diminutive of Tadeusz) | Statement: [Tadzio, hasSurname, Tadzio (diminutive of Tadeusz)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tadzio (diminutive of Tadeusz) Context triple: [Tadzio, hasSurname, Tadzio (diminutive of Tadeusz)]
-
A.
Tomasz
Tomasz is a masculine given name of Aramaic origin, widely used in Poland and other European countries, equivalent to the English name Thomas.
-
B.
Wojciech
Wojciech is a masculine given name of Slavic origin, particularly common in Poland.
-
C.
Tadeusz
chosen
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
D.
Michał
Michał is a Polish given name commonly used for males, equivalent to the English name Michael.
-
E.
Józef
Józef is a masculine given name of Hebrew origin, widely used in Poland and other Slavic countries as a form of Joseph.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c2b9bc81909a4ce91792294d1c |
completed | April 1, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1013279d88190aac1d25cc6aeb1fb |
completed | April 4, 2026, 12:16 p.m. |
Created at: March 30, 2026, 7:47 p.m.