Triple
T12967304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel Korzeniowski |
E321294
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Korzeniowski |
E321294
|
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: Korzeniowski | Statement: [Abel Korzeniowski, familyName, Korzeniowski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Korzeniowski Context triple: [Abel Korzeniowski, familyName, Korzeniowski]
-
A.
Korzeniowski
chosen
Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
-
B.
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.
-
C.
Ogiński
Ogiński is the surname of a prominent Polish–Lithuanian noble family best known for composer and statesman Michał Kleofas Ogiński.
-
D.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
E.
Wasilewski
Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e3f702481908f0f90f4f12d3f4d |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6eacea664819096940ba4d409d264 |
completed | May 3, 2026, 6:27 a.m. |
Created at: April 9, 2026, 8:30 p.m.