Triple
T32051113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sto. Tomas de Villanueva Parish Church |
E818494
|
entity |
| Predicate | municipalityPatron |
P52995
|
FINISHED |
| Object | Miagao |
—
|
NE NERFINISHED |
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: Miagao | Statement: [Sto. Tomas de Villanueva Parish Church, municipalityPatron, Miagao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityPatron Context triple: [Sto. Tomas de Villanueva Parish Church, municipalityPatron, Miagao]
-
A.
cityPatroness
Indicates that a female patron or protective figure is associated with and regarded as the guardian or benefactor of a particular city.
-
B.
cityPatron
chosen
Indicates that one entity serves as the patron, protector, or special guardian of a particular city.
-
C.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
D.
mainChurchPatron
Indicates that one entity serves as the primary patron or chief sponsoring supporter of a particular church.
-
E.
isMunicipalSymbolOf
Indicates that something serves as an official municipal symbol representing a particular city or local government.
- F. None of above.
Provenance (3 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:20 a.m.