Triple
T4677087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kura |
E103707
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Kür |
E82236
|
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: Kür | Statement: [Kura, alsoKnownAs, Kür]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kür Context triple: [Kura, alsoKnownAs, Kür]
-
A.
Kür
chosen
Kür is the Azerbaijani name for the Kura River, a major waterway flowing through Turkey, Georgia, and Azerbaijan into the Caspian Sea.
-
B.
Kurast
Kurast is a sprawling, jungle-clad port city and major quest hub in Diablo II, known for its corrupted temples, dense overgrowth, and role as the seat of Mephisto’s influence in the game’s third act.
-
C.
Kurz
Kurz is an alternative spelling or variant form of the name Kurtz, commonly used as a surname or character name in German-speaking contexts.
-
D.
Keres
Keres are female death-spirits from Greek mythology associated with violent death and the battlefield, often depicted as dark, bloodthirsty beings who seize the souls of the dying.
-
E.
Kut
Kut is a city in eastern Iraq situated on the banks of the Tigris River, known historically as a strategic location and the site of significant World War I battles.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd63698a548190831863adddd32f31 |
completed | March 20, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be03a0d5c88190a9b40e1ca7d165ff |
completed | March 21, 2026, 2:34 a.m. |
Created at: March 20, 2026, 1:16 p.m.