Triple
T17095322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanislaus |
E414832
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Stanisław |
E89797
|
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: Stanisław | Statement: [Stanislaus, hasVariantForm, Stanisław]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stanisław Context triple: [Stanislaus, hasVariantForm, Stanisław]
-
A.
Stanislaw
chosen
Stanislaw is a masculine given name of Slavic origin, most notably borne by the Polish-American mathematician Stanislaw Ulam.
-
B.
Bronisław
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
-
C.
Mieczysław
Mieczysław is a traditional Slavic male given name, particularly common in Poland, derived from elements meaning "sword" and "glory" or "fame."
-
D.
Józef
Józef is a masculine given name of Hebrew origin, widely used in Poland and other Slavic countries as a form of Joseph.
-
E.
Lucjan
Lucjan is a masculine given name of Latin origin, commonly used in Poland and other Slavic countries.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfc9158819081689d3d594a1908 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fbe1d4c81909ce7e4626516b51d |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:35 a.m.