Triple
T13836994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Δωροθέα |
E332554
|
entity |
| Predicate | isCognateWith |
P2527
|
FINISHED |
| Object | Doroteja |
E332555
|
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: Doroteja | Statement: [Δωροθέα, isCognateWith, Doroteja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doroteja Context triple: [Δωροθέα, isCognateWith, Doroteja]
-
A.
Doroteja
chosen
Doroteja is a feminine given name, commonly used in Slavic countries, that is a variant of the name Dorothea.
-
B.
Nadiža
Nadiža is a river in the western Balkans, known for its clear waters and scenic course through the mountainous border region between Slovenia and Italy.
-
C.
Dáša
Dáša is a common Czech and Slovak feminine given name, typically used as a diminutive form of Dagmar.
-
D.
Pavlina
Pavlina is a feminine given name, commonly used in Slavic countries as a variant of names like Paulina.
-
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 (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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029b352081909605baaedc336213 |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8f4318881909f6541f40ef87856 |
completed | May 3, 2026, 9:07 p.m. |
Created at: April 9, 2026, 10:13 p.m.