Triple
T16524569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man from St. Petersburg |
E401400
|
entity |
| Predicate | hasMainCharacter |
P1183
|
FINISHED |
| Object | Feliks |
E262438
|
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: Feliks | Statement: [The Man from St. Petersburg, hasMainCharacter, Feliks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feliks Context triple: [The Man from St. Petersburg, hasMainCharacter, Feliks]
-
A.
Feliks
chosen
Feliks is a given name, commonly used in Slavic and other European languages, that corresponds to the name Felix.
-
B.
Franek
Franek is a common Polish diminutive form of the male given name Franciszek.
-
C.
Ludwik
Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
-
D.
Janusz
Janusz is a masculine given name of Polish origin commonly used in Poland and among Polish communities.
-
E.
Ignacy
Ignacy is a masculine given name of Polish origin, historically borne by several notable figures including scientists, politicians, and religious leaders.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed323c081908218460aa4ae3cf6 |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00608b7f6081909912dd575979f8d7 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:14 a.m.