Triple

T35151608
Position Surface form Disambiguated ID Type / Status
Subject Vĩnh Tường District E1015007 entity
Predicate administrativeCenter P1474 FINISHED
Object Vĩnh Tường (town)
Vĩnh Tường is a township in northern Vietnam that serves as the main urban and political hub of Vĩnh Tường District in Vĩnh Phúc Province.
E2129638 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ĩnh Tường (town) | Statement: [Vĩnh Tường District, administrativeCenter, Vĩnh Tường (town)]
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ĩnh Tường (town)
Triple: [Vĩnh Tường District, administrativeCenter, Vĩnh Tường (town)]
Generated description
Vĩnh Tường is a township in northern Vietnam that serves as the main urban and political hub of Vĩnh Tường District in Vĩnh Phúc Province.

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_69f76ddb3a708190b521ba2970b17178 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78cecd0d08190bcb21d5b53d232e8 completed May 3, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37fb0dc08c819094b62d725de85f99 completed June 21, 2026, 2:54 p.m.
NEDg Description generation batch_6a37fc128968819088382c45052692ee completed June 21, 2026, 2:58 p.m.
NED2 Entity disambiguation (via description) batch_6a37fcd7cb108190bb34b69ce43aafed completed June 21, 2026, 3:01 p.m.
Created at: May 3, 2026, 4:02 p.m.