Triple
T23851172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O.Cist. |
E592170
|
entity |
| Predicate | religiousOrderRite |
P81280
|
FINISHED |
| Object | Latin 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: Latin Rite | Statement: [O.Cist., religiousOrderRite, Latin Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderRite Context triple: [O.Cist., religiousOrderRite, Latin Rite]
-
A.
religiousOrderOrRole
Indicates that an entity has a specific religious affiliation, order, or role within a religious tradition.
-
B.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
C.
ordinationRite
chosen
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
D.
religiousOrderAssociation
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
E.
religiousOrderBranchOf
Indicates that one religious order or congregation is an official subdivision, branch, or offshoot of another religious order.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.