Triple
T11989115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feliks Kon |
E285358
|
entity |
| Predicate | givenName |
P17
|
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: [Feliks Kon, givenName, Feliks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feliks Context triple: [Feliks Kon, givenName, Feliks]
-
A.
Feliks
chosen
Feliks is a given name, commonly used in Slavic and other European languages, that corresponds to the name Felix.
-
B.
Ludwik
Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
-
C.
Janusz
Janusz is a masculine given name of Polish origin commonly used in Poland and among Polish communities.
-
D.
Ignacy
Ignacy is a masculine given name of Polish origin, historically borne by several notable figures including scientists, politicians, and religious leaders.
-
E.
Jacek
Jacek is a common Polish male given name, often associated with notable figures in Polish politics, arts, and academia.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903ae28708190a826bad1624343eb |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f634515d20819094c9bc4f2c7cda8a |
completed | May 2, 2026, 5:28 p.m. |
Created at: April 8, 2026, 9:46 p.m.