Triple

T33560936
Position Surface form Disambiguated ID Type / Status
Subject Go Cong E859619 entity
Predicate locatedInFormerProvince P25414 FINISHED
Object Go Cong province
Go Cong province was a former administrative province in southern Vietnam that encompassed the Go Cong area before being merged into larger provincial units.
E2090844 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: Go Cong province | Statement: [Go Cong, locatedInFormerProvince, Go Cong province]
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: Go Cong province
Triple: [Go Cong, locatedInFormerProvince, Go Cong province]
Generated description
Go Cong province was a former administrative province in southern Vietnam that encompassed the Go Cong area before being merged into larger provincial units.

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_69f3497c1d288190a844ea699914e038 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f7127d848190916a5a45fe3b6578 completed May 3, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36f9a821d481908ffd5b01b0597793 completed June 20, 2026, 8:35 p.m.
NEDg Description generation batch_6a36fab9d4448190a49caae3e8f7c561 completed June 20, 2026, 8:40 p.m.
NED2 Entity disambiguation (via description) batch_6a36fb6882fc8190bd69194e3eabeb8f completed June 20, 2026, 8:43 p.m.
Created at: May 1, 2026, 1:40 a.m.