Triple
T35038281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syro-Malabar eparchies |
E1010989
|
entity |
| Predicate | areSuiIurisWithin |
P139868
|
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, areSuiIurisWithin, Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSuiIurisWithin Context triple: [Syro-Malabar eparchies, areSuiIurisWithin, Catholic Church]
-
A.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
B.
isWithinCivilJurisdiction
Indicates that one entity falls under the legal authority, control, or governance of a specified civil jurisdiction.
-
C.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
-
D.
suiIuris
chosen
Indicates that an entity possesses full legal independence or authority over itself, not being subject to the control or jurisdiction of another.
-
E.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
- 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.