Triple
T11059880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catharism |
E261480
|
entity |
| Predicate | layMembersCalled |
P6049
|
FINISHED |
| Object | 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: Believers | Statement: [Catharism, layMembersCalled, Believers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layMembersCalled Context triple: [Catharism, layMembersCalled, Believers]
-
A.
membersCalled
chosen
Indicates that specific members of a group or collection are being referred to or identified by a particular name or label.
-
B.
membersAreAppointedIn
Indicates that the members of a group or body are selected or assigned to their positions within a particular organization, institution, or context.
-
C.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
D.
allMembersAre
Indicates that every member of a specified group or set satisfies a given condition or belongs entirely to another specified group.
-
E.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication to another entity.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798e991848190b07c2f48dae38681 |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.