Triple

T24549339
Position Surface form Disambiguated ID Type / Status
Subject Archbishop of Huế E607315 entity
Predicate jurisdiction P82 FINISHED
Object Archdiocese of Huế
The Archdiocese of Huế is a major Roman Catholic ecclesiastical territory in central Vietnam, centered in the city of Huế and led by an archbishop.
E1640016 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: Archdiocese of Huế | Statement: [Archbishop of Huế, jurisdiction, Archdiocese of Huế]
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: Archdiocese of Huế
Triple: [Archbishop of Huế, jurisdiction, Archdiocese of Huế]
Generated description
The Archdiocese of Huế is a major Roman Catholic ecclesiastical territory in central Vietnam, centered in the city of Huế and led by an archbishop.

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_69e2c4c9bf94819082d05da6f5c29907 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8cc2838819087d3fd429f12b525 completed April 30, 2026, 12:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0ff85cf854819091b4adc0cb083a48 completed May 22, 2026, 6:31 a.m.
NEDg Description generation batch_6a0ff91ca7ac8190a5a42198badb6db4 completed May 22, 2026, 6:35 a.m.
NED2 Entity disambiguation (via description) batch_6a0ff9a53da081908bd4dd7bc4dd8143 completed May 22, 2026, 6:37 a.m.
Created at: April 18, 2026, 2:27 a.m.