Triple
T27195457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simbang Gabi |
E683584
|
entity |
| Predicate | devotionalElement |
P162244
|
FINISHED |
| Object | special prayers for families |
—
|
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: special prayers for families | Statement: [Simbang Gabi, devotionalElement, special prayers for families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalElement Context triple: [Simbang Gabi, devotionalElement, special prayers for families]
-
A.
devotionalElement
chosen
Indicates a relationship where something serves as or functions as an element used in devotional or religious practice.
-
B.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
C.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
D.
devotionalCollection
Indicates that one entity is a curated set or compilation of devotional items, works, or practices associated with another entity.
-
E.
devotionalFormat
Indicates the specific structure or style in which a devotional practice, text, or activity is organized or presented.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625af81808190af840a2eab1aff15 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:34 a.m.