Triple
T5813793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abhay Charan De |
E128933
|
entity |
| Predicate | hasReligionPosition |
P37107
|
FINISHED |
| Object | acharya in Gaudiya Vaishnavism |
—
|
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: acharya in Gaudiya Vaishnavism | Statement: [Abhay Charan De, hasReligionPosition, acharya in Gaudiya Vaishnavism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionPosition Context triple: [Abhay Charan De, hasReligionPosition, acharya in Gaudiya Vaishnavism]
-
A.
positionInReligion
chosen
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
B.
positionOnStateReligion
Indicates a stance or viewpoint regarding the role, status, or legitimacy of an official state religion.
-
C.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
D.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
E.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:52 p.m.