Triple
T22855481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karol Świerczewski |
E566467
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Świerczewski |
—
|
NE NERFINISHED |
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: Świerczewski | Statement: [Karol Świerczewski, familyName, Świerczewski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Świerczewski Context triple: [Karol Świerczewski, familyName, Świerczewski]
-
A.
Świerczewski
chosen
Świerczewski is a Polish surname most notably associated with Karol Świerczewski, a Polish-Soviet military officer and communist activist.
-
B.
Szewczyk
Szewczyk is a Polish surname of occupational origin, historically associated with shoemakers or cobblers.
-
C.
Skrzyński
Skrzyński is a Polish surname most notably associated with Aleksander Skrzyński, a prominent early 20th-century Polish politician and diplomat.
-
D.
Pietraszewicz
Pietraszewicz is a Polish surname associated with individuals such as Bronisław "Lot" Pietraszewicz.
-
E.
Żółkiewski
Żółkiewski is a Polish noble surname most famously associated with the hetman and statesman Stanisław Żółkiewski of the Polish–Lithuanian Commonwealth.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebc6a088190890f2474f18a10eb |
completed | April 29, 2026, 3:45 a.m. |
Created at: April 17, 2026, 3:37 p.m.