Triple
T30292130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C.R. |
E770406
|
entity |
| Predicate | orderReligiousFamily |
P175366
|
FINISHED |
| Object | Roman Catholic religious orders |
—
|
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: Roman Catholic religious orders | Statement: [C.R., orderReligiousFamily, Roman Catholic religious orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderReligiousFamily Context triple: [C.R., orderReligiousFamily, Roman Catholic religious orders]
-
A.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
B.
orderReligion
Indicates that one entity prescribes, organizes, or regulates the religious practices, beliefs, or structure of another entity.
-
C.
religiousFamilyBackground
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
-
D.
religiousOrderFamilyType
Indicates the type or category of religious order to which a given religious family or group belongs.
-
E.
fatherReligion
Indicates the religious affiliation or belief system practiced or identified with by a person's father.
- F. None of above. chosen
Provenance (4 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 7:47 p.m.