Triple
T17047036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonasz Szlichtyng |
E413596
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Jonasz |
E413596
|
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: Jonasz | Statement: [Jonasz Szlichtyng, givenName, Jonasz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jonasz Context triple: [Jonasz Szlichtyng, givenName, Jonasz]
-
A.
Janusz
Janusz is a masculine given name of Polish origin commonly used in Poland and among Polish communities.
-
B.
Jacek
Jacek is a common Polish male given name, often associated with notable figures in Polish politics, arts, and academia.
-
C.
Jonasz Szlichtyng
chosen
Jonasz Szlichtyng was a 17th-century Polish Arian theologian and writer known for his influential works defending nontrinitarian beliefs.
-
D.
Szymon
Szymon is a masculine given name of Hebrew origin, commonly used in Poland and other Slavic countries as a variant of Simon.
-
E.
Jarek
Jarek is a masculine given name, commonly used in Slavic countries, often as a diminutive or variant of names like Jarosław.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9e3d8881909f197aba0e4c97e7 |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ed472d48190bc6aed49464dc1ff |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.