Triple
T17324550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Merlin |
E420651
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wasylewski |
—
|
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: Wasylewski | Statement: [Jan Merlin, familyName, Wasylewski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wasylewski Context triple: [Jan Merlin, familyName, Wasylewski]
-
A.
Wasilewski
chosen
Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
-
B.
Pietraszewicz
Pietraszewicz is a Polish surname associated with individuals such as Bronisław "Lot" Pietraszewicz.
-
C.
Korzeniowski
Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
-
D.
Wiazemsky
Wiazemsky is a French surname most notably associated with actress and novelist Anne Wiazemsky, known for her work in 1960s and 1970s European cinema and literature.
-
E.
Kowalik
Kowalik is a Polish surname, likely of similar origin or family line to the surname Kowalski.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d18e3081908ca15baa743abcd8 |
completed | April 19, 2026, 2:11 a.m. |
Created at: April 10, 2026, 5:43 a.m.