Triple
T14714575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tania |
E345642
|
entity |
| Predicate | isDistinctFrom |
P1612
|
FINISHED |
| Object | Tanja |
E1115742
|
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: Tanja | Statement: [Tania, isDistinctFrom, Tanja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tanja Context triple: [Tania, isDistinctFrom, Tanja]
-
A.
Tanja
chosen
Tanja is a feminine given name commonly used in various European countries, often as a variant of Tatjana or Tanya.
-
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.
Anja
Anja is a feminine given name commonly used in various European countries, often considered a variant of Anna.
-
D.
Dáša
Dáša is a common Czech and Slovak feminine given name, typically used as a diminutive form of Dagmar.
-
E.
Dunja
Dunja is a feminine given name commonly used in South Slavic countries, often associated with the Bosnian human rights advocate Dunja Mijatović.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe388792688190b1b6eaa8091733fb |
completed | May 8, 2026, 7:24 p.m. |
Created at: April 10, 2026, 1:29 a.m.