Triple

T32306694
Position Surface form Disambiguated ID Type / Status
Subject Prome District (historical) E825389 entity
Predicate containedTownship P22464 FINISHED
Object Padigon Township
Padigon Township was an administrative subdivision within the former Prome District in British Burma, in what is now central Myanmar.
E2009560 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: Padigon Township | Statement: [Prome District (historical), containedTownship, Padigon Township]
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: Padigon Township
Triple: [Prome District (historical), containedTownship, Padigon Township]
Generated description
Padigon Township was an administrative subdivision within the former Prome District in British Burma, in what is now central Myanmar.

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_69f349115304819084ee91d345b6c8aa completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ffc1b9581c8190abfa89b30340a641 completed May 9, 2026, 11:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a34703daedc8190a57e9225fbdd1ec4 completed June 18, 2026, 10:25 p.m.
NEDg Description generation batch_6a347215d4b881909c3079cb6961de60 completed June 18, 2026, 10:32 p.m.
NED2 Entity disambiguation (via description) batch_6a3472763f748190adc26a4621f7352c completed June 18, 2026, 10:34 p.m.
Created at: May 1, 2026, 12:45 a.m.