Triple
T13441982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacek |
E320384
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Jacek (English transliteration) |
E320384
|
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: Jacek (English transliteration) | Statement: [Jacek, hasVariant, Jacek (English transliteration)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jacek (English transliteration) Context triple: [Jacek, hasVariant, Jacek (English transliteration)]
-
A.
Jacek
chosen
Jacek is a common Polish male given name, often associated with notable figures in Polish politics, arts, and academia.
-
B.
Jarek
Jarek is a masculine given name, commonly used in Slavic countries, often as a diminutive or variant of names like Jarosław.
-
C.
Janek
Janek is the gruff but good-natured captain of the spaceship Prometheus in Ridley Scott’s 2012 science fiction film.
-
D.
Jerzy
Jerzy is a masculine given name of Slavic origin, particularly common in Poland as the equivalent of George.
-
E.
Sławek
Sławek is a Polish surname most notably borne by Walery Sławek, a prominent early 20th-century Polish politician and close associate of Józef Piłsudski.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7399421908190a7750e37c89a73f6 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.