Triple
T12758759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadeusz Kasprzycki |
E304931
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | 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: Tadeusz | Statement: [Tadeusz Kasprzycki, givenName, Tadeusz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tadeusz Context triple: [Tadeusz Kasprzycki, givenName, Tadeusz]
-
A.
Tadeusz
chosen
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
B.
Timoteusz
Timoteusz is a masculine given name, primarily used in Polish and other Slavic languages, derived from the Greek-origin name Timothy.
-
C.
Jędrzej
Jędrzej is a Polish male given name, traditionally used as a regional or archaic form of the name Andrzej (Andrew).
-
D.
Walery
Walery is a masculine given name of Slavic origin, used primarily in Polish-speaking countries.
-
E.
Korzeniowski
Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8d3eb08190ae998df5cc6d9ba6 |
completed | April 10, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b8e89cc8190ac97b13d9d409179 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:27 p.m.