Triple
T12244819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henryk Sucharski |
E291824
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Henryk |
E298594
|
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: Henryk | Statement: [Henryk Sucharski, givenName, Henryk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henryk Context triple: [Henryk Sucharski, givenName, Henryk]
-
A.
Henryk
chosen
Henryk is a masculine given name of Germanic origin commonly used in Poland and other Central and Eastern European countries.
-
B.
Ludwik
Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
-
C.
Horsztyński
"Horsztyński" is a dramatic work by Polish Romantic poet and playwright Juliusz Słowacki, reflecting his characteristic themes of patriotism, inner conflict, and national struggle.
-
D.
Jerzy
Jerzy is a masculine given name of Slavic origin, particularly common in Poland as the equivalent of George.
-
E.
Wiktor
Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb724448190be29fc1d2b946ab7 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60ab7b9308190b621b71d75aa10cc |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.