Triple
T23806961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Of the Universal Church |
E589734
|
entity |
| Predicate | concernsRite |
P148709
|
FINISHED |
| Object | Roman Rite |
—
|
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: Roman Rite | Statement: [Of the Universal Church, concernsRite, Roman Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsRite Context triple: [Of the Universal Church, concernsRite, Roman Rite]
-
A.
concernedRite
chosen
Indicates that a rite, ritual, or ceremonial act is the focus or subject of concern, involvement, or relevance in the relationship.
-
B.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
C.
concernsTitle
Indicates that something is about or relates specifically to a particular title (such as a name, designation, or formal heading).
-
D.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
E.
concernsProvision
Indicates a relationship where something is about, deals with, or relates to the supplying or making available of resources, services, or necessities.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c752ff6481908cfc20d4f178d526 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.