Triple
T17957667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuru Kingdom |
E448995
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Kuru (mythical ancestor) |
—
|
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: Kuru (mythical ancestor) | Statement: [Kuru Kingdom, namedAfter, Kuru (mythical ancestor)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuru (mythical ancestor) Context triple: [Kuru Kingdom, namedAfter, Kuru (mythical ancestor)]
-
A.
Kur
Kur is the ancient Mesopotamian underworld, a dark subterranean realm of the dead ruled by the goddess Ereshkigal.
-
B.
King Kuru
chosen
King Kuru is a legendary ancestral monarch in Indian epic tradition, regarded as the progenitor of the Kuru clan central to the Mahabharata.
-
C.
Kamsa
Kamsa is a tyrannical king in Hindu mythology, best known as the evil uncle and nemesis of Lord Krishna.
-
D.
Kor
Kor is a prominent Klingon warrior and commander from the Star Trek franchise, known as one of the earliest and most iconic Klingon characters in the series.
-
E.
Kuresa
Kuresa, also known by the honorific Koorathazhwan, was a prominent 11th-century Sri Vaishnava scholar and chief disciple of the theologian Ramanuja.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afb16bfc8190b3eb433a90f0630d |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 10:21 a.m.