Triple
T11976350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jędrzej |
E285049
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Jendrzej |
E285049
|
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: Jendrzej | Statement: [Jędrzej, hasVariantSpelling, Jendrzej]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jendrzej Context triple: [Jędrzej, hasVariantSpelling, Jendrzej]
-
A.
Janusz
Janusz is a masculine given name of Polish origin commonly used in Poland and among Polish communities.
-
B.
Jędrzej
chosen
Jędrzej is a Polish male given name, traditionally used as a regional or archaic form of the name Andrzej (Andrew).
-
C.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
D.
Lopatynski
Lopatynski is the original Polish family name of Eddie Lopat, a notable Major League Baseball pitcher and later coach.
-
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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903926690819090e7ce982f103457 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f471f6afc48190856a0f7c486b28aa |
completed | May 1, 2026, 9:27 a.m. |
Created at: April 8, 2026, 9:46 p.m.