Triple
T35038280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syro-Malabar eparchies |
E1010989
|
entity |
| Predicate | areCommunionWith |
P3104
|
FINISHED |
| Object | Catholic Church |
—
|
NE NERFINISHED |
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: Catholic Church | Statement: [Syro-Malabar eparchies, areCommunionWith, Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areCommunionWith Context triple: [Syro-Malabar eparchies, areCommunionWith, Catholic Church]
-
A.
communionWith
chosen
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
B.
communion
Indicates a close, often spiritual or emotional sharing or union between entities.
-
C.
hasCommunion
Indicates that one entity shares or participates in a close, often spiritual or sacramental, union or fellowship with another entity.
-
D.
partOfCommunion
Indicates that an entity participates in or belongs to a specific communion, such as a religious or sacramental union.
-
E.
communionContext
Indicates the situational or ceremonial setting in which a communion event or act takes place.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858f4eac8190a71bc6fddd380cda |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.