Triple

T890259
Position Surface form Disambiguated ID Type / Status
Subject Nagpur E19222 entity
Predicate namedAfter P63 FINISHED
Object Nag River E221759 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: Nag River | Statement: [Nagpur, namedAfter, Nag River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nag River
Context triple: [Nagpur, namedAfter, Nag River]
  • A. Nag River chosen
    Nag River is a river in the Indian state of Maharashtra that flows through the city of Nagpur and is considered central to the city's historical identity and name.
  • B. Shire River
    The Shire River is a major river in Malawi that drains Lake Malawi and flows southward into Mozambique, where it joins the Zambezi River.
  • C. Manyame River
    The Manyame River is a major river in northern Zimbabwe that flows near the capital city of Harare and feeds into Lake Manyame, an important water source for the region.
  • D. Situk River
    The Situk River is a renowned Alaskan river famous for its pristine waters and exceptional wild salmon and steelhead fishing.
  • E. Banas River
    The Banas River is a significant river in northwestern India that flows through Rajasthan as a major tributary of the Chambal River.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad0086a081908c47c285896a1f3c completed March 1, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae0a910d808190b20150e864ae9bc2 completed March 8, 2026, 11:47 p.m.
Created at: March 1, 2026, 7:39 p.m.