Triple
T18424871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Ivanovich Maximowicz |
E442110
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Maximowicz |
—
|
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: Maximowicz | Statement: [Karl Ivanovich Maximowicz, familyName, Maximowicz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maximowicz Context triple: [Karl Ivanovich Maximowicz, familyName, Maximowicz]
-
A.
Maximowicz
chosen
Maximowicz was a 19th-century Russian botanist and explorer known for his extensive taxonomic work on East Asian flora.
-
B.
Korzeniowski
Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
-
C.
Gorgolewski
Gorgolewski is a Polish surname most notably borne by architect Zygmunt Gorgolewski, known for his influential work in Central and Eastern Europe.
-
D.
Wasilewski
Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
-
E.
Michniewicz
Michniewicz is a Polish surname most notably borne by football manager Czesław Michniewicz.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51b1149788190ad7c453547a6e07c |
completed | April 19, 2026, 6:12 p.m. |
Created at: April 10, 2026, 10:47 a.m.