Triple

T3190372
Position Surface form Disambiguated ID Type / Status
Subject Nanchang E66806 entity
Predicate locatedOnRiver P165 FINISHED
Object Gan River E219885 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: Gan River | Statement: [Nanchang, locatedOnRiver, Gan River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Gan River
Context triple: [Nanchang, locatedOnRiver, Gan River]
  • A. Gan River chosen
    The Gan River is a major river in southeastern China that flows through Jiangxi Province and ultimately feeds into the Yangtze River system.
  • B. Kameng River
    Kameng River is a major Himalayan river in northeastern India that flows through Arunachal Pradesh and Assam before joining the Brahmaputra.
  • C. Shinfa River
    The Shinfa River is a tributary watercourse that feeds into the Atbara River in northeastern Africa.
  • D. Zi River
    The Zi River is a major river in south-central China that flows through Hunan Province and is one of the important tributaries of the Yangtze River system.
  • E. Yan River
    The Yan River is a tributary of the Yellow River in Shaanxi Province, China, known for flowing through the historic revolutionary base area of Yan'an.
  • 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_69ad8588ba18819086a10951c32ecb80 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6e7d0d081908b1c36bb909a58bf completed March 8, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4dae9a0cc8190acc56eaa4f2479ef completed March 14, 2026, 3:50 a.m.
Created at: March 8, 2026, 3:07 p.m.