Triple
T14013507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Konstanty |
E337146
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Konstanty |
E928364
|
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: Konstanty | Statement: [Jim Konstanty, familyName, Konstanty]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konstanty Context triple: [Jim Konstanty, familyName, Konstanty]
-
A.
Konstanty
chosen
Konstanty is a masculine given name of Slavic origin, commonly used in Poland and other Central and Eastern European countries.
-
B.
Bronisław
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
-
C.
Stanislas of Szczepanów
Stanislas of Szczepanów, also known as Saint Stanislaus, was an 11th-century Bishop of Kraków and martyr who became one of Poland’s principal patron saints.
-
D.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
-
E.
Wincenty
Wincenty is a masculine given name of Slavic origin, particularly common in Poland.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb653fedc81908cdd0dde2d3f3329 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:19 p.m.