Triple
T18807225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaudia |
E459904
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Klaudija |
—
|
NE NERFINISHED |
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: Klaudija | Statement: [Klaudia, hasVariantSpelling, Klaudija]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klaudija Context triple: [Klaudia, hasVariantSpelling, Klaudija]
-
A.
Klaudija
chosen
Klaudija is a feminine given name, commonly used in Slavic countries, that corresponds to the name Claudia.
-
B.
Klaudia
Klaudia is the feminine given name corresponding to the male name Klaus, commonly used in various European countries.
-
C.
Julijana
Julijana is a feminine given name, commonly used in Slavic countries, that corresponds to the name Juliana in other languages.
-
D.
Dagmara
Dagmara is a feminine given name, primarily used in Slavic countries, that is a variant of the name Dagmar.
-
E.
Emilija
Emilija is a feminine given name commonly used in various Slavic and Baltic countries, equivalent to Emilia or Emily in English.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d8ab9c819097834eac798ce810 |
completed | April 20, 2026, 3:56 a.m. |
Created at: April 10, 2026, 11:53 a.m.