Triple

T31070242
Position Surface form Disambiguated ID Type / Status
Subject Vàm Cỏ Đông River E791795 entity
Predicate tributaryOf P415 FINISHED
Object Vàm Cỏ River
The Vàm Cỏ River is a major river system in southern Vietnam that flows through the Mekong Delta region and supports extensive agriculture, transportation, and local livelihoods.
 E2296319 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: Vàm Cỏ River | Statement: [Vàm Cỏ Đông River, tributaryOf, Vàm Cỏ River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Vàm Cỏ River
Triple: [Vàm Cỏ Đông River, tributaryOf, Vàm Cỏ River]
Generated description
The Vàm Cỏ River is a major river system in southern Vietnam that flows through the Mekong Delta region and supports extensive agriculture, transportation, and local livelihoods.

Provenance (5 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_69f224cc0c5c81908404f087bff92997 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f695b566388190a0e6018bf397aa67 completed May 3, 2026, 12:24 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82629a260c8190b5c026466e40fbb1 completed Aug. 17, 2026, 1:23 a.m.
NEDg Description generation batch_6a8262f489b88190a7a16c6c40d9983e completed Aug. 17, 2026, 1:25 a.m.
NED2 Entity disambiguation (via description) batch_6a82634655c48190be7c991c6ce2cf4e completed Aug. 17, 2026, 1:26 a.m.
Created at: April 29, 2026, 9:01 p.m.