Triple
T20797098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCD |
E511939
|
entity |
| Predicate | religiousOrderCharism |
P57647
|
FINISHED |
| Object | contemplative life |
—
|
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: contemplative life | Statement: [OCD, religiousOrderCharism, contemplative life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderCharism Context triple: [OCD, religiousOrderCharism, contemplative life]
-
A.
foundingCharism
chosen
Indicates the distinctive spiritual focus, mission, or guiding gift that characterizes the founding identity of a religious community or organization.
-
B.
religiousOrderFeatured
Indicates that a religious order is prominently highlighted, showcased, or given special attention in relation to another entity or context.
-
C.
religiousOrderOrRole
Indicates that an entity has a specific religious affiliation, order, or role within a religious tradition.
-
D.
religiousOrderName
Indicates the specific name of the religious order with which an entity is affiliated or associated.
-
E.
religiousOrderInfluence
Indicates that one religious order exerts influence, guidance, or control over another entity, such as a person, group, or institution.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ad6f0481909e0bab7119f10f9c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.