Triple

T34093644
Position Surface form Disambiguated ID Type / Status
Subject Province of Negros Occidental E874363 entity
Predicate hasMunicipality P847 FINISHED
Object San Enrique
San Enrique is a municipality in the Philippine province of Negros Occidental known for its predominantly agricultural economy and rural communities.
E2080746 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: San Enrique | Statement: [Province of Negros Occidental, hasMunicipality, San Enrique]
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: San Enrique
Triple: [Province of Negros Occidental, hasMunicipality, San Enrique]
Generated description
San Enrique is a municipality in the Philippine province of Negros Occidental known for its predominantly agricultural economy and rural communities.

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_69f349a735208190a1dbfb1c2a121059 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70c5676648190b2bee263bbc8ec7d completed May 3, 2026, 8:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae5e49d48190886632f1850b9118 completed June 20, 2026, 3:14 p.m.
NEDg Description generation batch_6a36aef70cac81909864ca6c04cbfa2a completed June 20, 2026, 3:17 p.m.
NED2 Entity disambiguation (via description) batch_6a36afc47fc4819097fd115ba24b55dc completed June 20, 2026, 3:20 p.m.
Created at: May 1, 2026, 1:52 a.m.