Triple
T29186370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaura Nitai |
E739878
|
entity |
| Predicate | roleInISKCON |
P137516
|
FINISHED |
| Object | Common household deities |
—
|
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: Common household deities | Statement: [Gaura Nitai, roleInISKCON, Common household deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInISKCON Context triple: [Gaura Nitai, roleInISKCON, Common household deities]
-
A.
roleInGaudiyaVaishnavism
chosen
Indicates the specific function, position, or significance an entity holds within the theological, devotional, or institutional framework of Gaudiya Vaishnavism.
-
B.
roleInRamakrishnaMovement
Indicates that an entity holds or has held a specific role or function within the Ramakrishna Movement.
-
C.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
D.
roleInBrahmoSamaj
Indicates that an entity holds or held a specific position, function, or involvement within the Brahmo Samaj movement or organization.
-
E.
roleInBhagavataPurana
Indicates the specific narrative or functional role an entity plays within the text of the Bhagavata Purana.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 28, 2026, noon