Triple
T250464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iglesia ni Cristo |
E5134
|
entity |
| Predicate | worshipPractice |
P1105
|
FINISHED |
| Object | congregational singing |
—
|
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: congregational singing | Statement: [Iglesia ni Cristo, worshipPractice, congregational singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipPractice Context triple: [Iglesia ni Cristo, worshipPractice, congregational singing]
-
A.
worshipStyle
chosen
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
B.
worshipImplication
Indicates that one entity’s worship, reverence, or devotional behavior toward another implies or entails a particular belief, status, or relationship between them.
-
C.
liturgicalServices
Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity or context.
-
D.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
E.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.