Triple
T9035320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wincenty |
E216476
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Wincent |
E216476
|
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: Wincent | Statement: [Wincenty, hasVariant, Wincent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wincent Context triple: [Wincenty, hasVariant, Wincent]
-
A.
Wincenty
chosen
Wincenty is a masculine given name of Slavic origin, particularly common in Poland.
-
B.
Wiktor
Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
-
C.
Ludwik
Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
-
D.
Witos
Witos is a Polish surname most notably borne by Wincenty Witos, a prominent early 20th-century Polish politician and three-time Prime Minister.
-
E.
Ignacy
Ignacy is a masculine given name of Polish origin, historically borne by several notable figures including scientists, politicians, and religious leaders.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6abf4af481908d21245332329d99 |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdbce352c8190b5862d0cc103bfdb |
completed | April 3, 2026, 3:25 p.m. |
Created at: March 30, 2026, 7:08 p.m.