Triple
T4930828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanuman Jayanti |
E110689
|
entity |
| Predicate | associatedQualityOfHanuman |
P50780
|
FINISHED |
| Object | bhakti (devotion) to Rama |
—
|
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: bhakti (devotion) to Rama | Statement: [Hanuman Jayanti, associatedQualityOfHanuman, bhakti (devotion) to Rama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedQualityOfHanuman Context triple: [Hanuman Jayanti, associatedQualityOfHanuman, bhakti (devotion) to Rama]
-
A.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
-
D.
associatedWithQuality
chosen
Indicates that an entity is linked to, characterized by, or possesses a particular quality or attribute.
-
E.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.