Triple
T4035424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Conrad |
E83816
|
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: [Joseph Conrad, familyName, Korzeniowski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Korzeniowski Context triple: [Joseph Conrad, familyName, Korzeniowski]
-
A.
Korzeniowski
chosen
Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
-
B.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
C.
Żymierski
Żymierski is a Polish surname most notably associated with Michał Rola-Żymierski, a high-ranking military commander and communist-era Marshal of Poland.
-
D.
Kowale Oleckie
Kowale Oleckie is a village in northern Poland that serves as the seat of its local administrative district within the Warmian-Masurian Voivodeship.
-
E.
Wiktor
Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb132f6c8190937acd35a6a5a9e4 |
completed | March 9, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5629748d88190984cce08eef05e9c |
completed | March 14, 2026, 1:28 p.m. |
Created at: March 9, 2026, 3:36 p.m.