Triple
T27088356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipolo Cathedral |
E686094
|
entity |
| Predicate | liturgicalFeastMonth |
P143315
|
FINISHED |
| Object | May |
—
|
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: May | Statement: [Antipolo Cathedral, liturgicalFeastMonth, May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalFeastMonth Context triple: [Antipolo Cathedral, liturgicalFeastMonth, May]
-
A.
liturgicalMonth
Indicates that something is associated with, occurs in, or pertains to a specific month within a liturgical or religious calendar.
-
B.
liturgicalFeastDay
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
C.
majorFestivalMonthGregorian
chosen
Indicates the Gregorian calendar month in which a major festival associated with an entity takes place.
-
D.
liturgicalFeastType
Indicates the specific category or type of liturgical feast to which a given religious celebration or observance belongs.
-
E.
liturgicalCalendarFocus
Indicates the primary religious observance, theme, or commemoration that a liturgical calendar entry is centered on.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623480110819088369af135123c24 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:39 a.m.