Triple
T33542668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Malolos |
E859112
|
entity |
| Predicate | notableChurchLocation |
P206510
|
FINISHED |
| Object | Malolos, Bulacan |
E385995
|
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: Malolos, Bulacan | Statement: [Roman Catholic Diocese of Malolos, notableChurchLocation, Malolos, Bulacan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChurchLocation Context triple: [Roman Catholic Diocese of Malolos, notableChurchLocation, Malolos, Bulacan]
-
A.
parishChurchLocation
Indicates the specific place where a parish church is situated or located.
-
B.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
-
C.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
D.
cathedralLocatedIn
Indicates that a cathedral is situated within or belongs to a specific geographic or administrative location.
-
E.
locatedInTheChurch
Indicates that one entity is physically situated within or inside the church.
- F. None of above. chosen
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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a361186bbfc8190ada8b6871676b7dd |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:39 a.m.