Triple
T2824100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrzej Witos |
E54878
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Witos |
E204499
|
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: Witos | Statement: [Andrzej Witos, familyName, Witos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Witos Context triple: [Andrzej Witos, familyName, Witos]
-
A.
Witos
chosen
Witos is a Polish surname most notably borne by Wincenty Witos, a prominent early 20th-century Polish politician and three-time Prime Minister.
-
B.
Wiktor
Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
-
C.
Gietrzwałd
Gietrzwałd is a village in northern Poland known as a Catholic pilgrimage site due to reported Marian apparitions in 1877.
-
D.
Wilkasy
Wilkasy is a village and popular lakeside tourist resort in northeastern Poland’s Warmian-Masurian Voivodeship, known for its marinas and access to the Masurian Lake District.
-
E.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde91487881909989c08bbf76f0da |
completed | March 7, 2026, 8:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afcead12588190bfbb2c9e93b05e0d |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:59 p.m.