Triple
T12390453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Reglas de Congo |
E295978
|
entity |
| Predicate | hasReligiousType |
P104709
|
FINISHED |
| Object | spiritist tradition |
—
|
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: spiritist tradition | Statement: [Las Reglas de Congo, hasReligiousType, spiritist tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousType Context triple: [Las Reglas de Congo, hasReligiousType, spiritist tradition]
-
A.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
B.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
C.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
D.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
E.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd0bcc48190bb1a59a3aaa6bfdf |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.