Triple
T715297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Catholic Church of Italy |
E14299
|
entity |
| Predicate | maintainsPractice |
P10364
|
FINISHED |
| Object | Catholic sacramental theology |
—
|
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: Catholic sacramental theology | Statement: [Old Catholic Church of Italy, maintainsPractice, Catholic sacramental theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsPractice Context triple: [Old Catholic Church of Italy, maintainsPractice, Catholic sacramental theology]
-
A.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
B.
isPracticedBy
chosen
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
C.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
E.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a574b4d881908b6d0be386081efd |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.