Triple
T4533385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuru dynasty |
E106349
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Kuru |
E449618
|
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: Kuru | Statement: [Kuru dynasty, namedAfter, Kuru]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuru Context triple: [Kuru dynasty, namedAfter, Kuru]
-
A.
Kuru
chosen
Kuru refers to an ancient Indo-Aryan tribe and kingdom of northern India, prominently featured in the Mahabharata as the ancestral lineage of the Kauravas and Pandavas.
-
B.
Tshilamoya
Tshilamoya is the popular nickname of Highlanders F.C., one of Zimbabwe’s oldest and most successful football clubs.
-
C.
Surra
Surra is a residential district in Kuwait City known for its central location and mix of housing, schools, and local services.
-
D.
House of Kuru
The House of Kuru is the royal dynasty at the center of the Indian epic Mahabharata, encompassing figures like the Pandavas and Kauravas and serving as the backdrop for the Kurukshetra War.
-
E.
Kankia
Kankia is a town and local government area in northern Nigeria, known for its role as an administrative and commercial center within Katsina State.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57a08ec4819091b84d53d7b564a7 |
completed | March 20, 2026, 2:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdacea41bc8190b49c9d1a31d7930f |
completed | March 20, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:04 p.m.