Triple
T18002247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Pasig |
E430655
|
entity |
| Predicate | canonicalErectionDate |
P130085
|
FINISHED |
| Object | 2003-08-21 |
—
|
LITERAL 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: 2003-08-21 | Statement: [Roman Catholic Diocese of Pasig, canonicalErectionDate, 2003-08-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalErectionDate Context triple: [Roman Catholic Diocese of Pasig, canonicalErectionDate, 2003-08-21]
-
A.
hasCanonicalErectionBy
Indicates that an entity’s standard or officially recognized form, structure, or establishment is brought about or instituted by another specified entity.
-
B.
hasCanonicalErectionAs
Indicates that one entity is recognized or defined as the standard or primary form of erection for another entity.
-
C.
reerectionDate
Indicates the date on which something that was previously removed, dismantled, or taken down is erected or put back up again.
-
D.
mayErect
Indicates that one entity is permitted or authorized to construct or put up another entity (such as a structure or installation).
-
E.
reignOfErection
Indicates a period or state during which an erection is present or dominant.
- F. None of above. chosen
Provenance (4 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b3e9498c8190bdfa7a53b0c0d8db |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.