Triple
T1689732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stan Mikita |
E36523
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Stanislav |
E192569
|
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: Stanislav | Statement: [Stan Mikita, givenName, Stanislav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stanislav Context triple: [Stan Mikita, givenName, Stanislav]
-
A.
Stanislav Guoth
chosen
Stanislav Guoth, better known as Stan Mikita, was a Slovak-born Canadian professional ice hockey player and Hall of Famer who became one of the Chicago Blackhawks’ greatest centers.
-
B.
Stanislaw
Stanislaw is a masculine given name of Slavic origin, most notably borne by the Polish-American mathematician Stanislaw Ulam.
-
C.
Miroslav
Miroslav is a common Slavic male given name, notably borne by Slovak ice hockey star Miroslav Šatan.
-
D.
Pavel
Pavel is a Slavic given name, equivalent to the English name Paul.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62979da48190a64a04bf352182e0 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5b9be4481908c0b6f030889edfb |
completed | March 8, 2026, 5:45 p.m. |
Created at: March 4, 2026, 7:29 p.m.