Triple

T14386047
Position Surface form Disambiguated ID Type / Status
Subject Indrapura E356725 entity
Predicate locatedNear P294 FINISHED
Object Thu Bon River E615137 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: Thu Bon River | Statement: [Indrapura, locatedNear, Thu Bon River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thu Bon River
Context triple: [Indrapura, locatedNear, Thu Bon River]
  • A. Thu Bon River chosen
    The Thu Bon River is a major waterway in central Vietnam that has historically supported trade, agriculture, and the cultural life of the ancient port town of Hoi An.
  • B. Luong River
    Luong River is a tributary waterway in Vietnam that feeds into the larger Ma River system.
  • C. Nhue River
    The Nhue River is a significant waterway in northern Vietnam that flows through the Red River Delta region, supporting agriculture, drainage, and daily life in provinces such as Ha Nam.
  • D. River Diem
    The River Diem is a small waterway in the Netherlands that flows through the town of Diemen near Amsterdam.
  • E. Tra Ly River
    The Tra Ly River is a significant waterway in northern Vietnam that flows through Thai Binh Province, supporting local agriculture, transportation, and livelihoods.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9025cff881908c08224d90d9f750 completed April 14, 2026, 7:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe0cd3aa20819089c8527faf1ceddd completed May 8, 2026, 4:18 p.m.
Created at: April 10, 2026, 1:16 a.m.