Triple
T3136289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignacy |
E65537
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Ignacy (with diacritics: none) |
E65537
|
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: Ignacy (with diacritics: none) | Statement: [Ignacy, hasVariant, Ignacy (with diacritics: none)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ignacy (with diacritics: none) Context triple: [Ignacy, hasVariant, Ignacy (with diacritics: none)]
-
A.
Ignacy
chosen
Ignacy is a masculine given name of Polish origin, historically borne by several notable figures including scientists, politicians, and religious leaders.
-
B.
Stanislaw
Stanislaw is a masculine given name of Slavic origin, most notably borne by the Polish-American mathematician Stanislaw Ulam.
-
C.
Wincenty
Wincenty is a masculine given name of Slavic origin, particularly common in Poland.
-
D.
Ignacio
Ignacio is a masculine given name of Spanish origin commonly used in Spanish-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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada564eacc8190a54d07b4eb31c196 |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f8793488190aa31040edaf1d627 |
completed | March 12, 2026, 12:57 a.m. |
Created at: March 8, 2026, 3:05 p.m.