Triple
T36596958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfects |
E902827
|
entity |
| Predicate | relationshipToBelievers |
P204954
|
FINISHED |
| Object | served lay Cathar believers |
—
|
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: served lay Cathar believers | Statement: [Perfects, relationshipToBelievers, served lay Cathar believers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToBelievers Context triple: [Perfects, relationshipToBelievers, served lay Cathar believers]
-
A.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
-
B.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
C.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
D.
ecclesialRelationship
Indicates a formal relationship or connection between entities within a church or ecclesiastical structure.
-
E.
partnerInReligiousLifeWith
Indicates that two individuals share a committed religious vocation or spiritual life together as partners.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.