Triple
T25553759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travancore royal family |
E640511
|
entity |
| Predicate | associatedDynasticReligion |
P21571
|
FINISHED |
| Object | Vaishnavism |
—
|
NE NERFINISHED |
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: Vaishnavism | Statement: [Travancore royal family, associatedDynasticReligion, Vaishnavism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynasticReligion Context triple: [Travancore royal family, associatedDynasticReligion, Vaishnavism]
-
A.
dynasticReligion
chosen
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
B.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
C.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
-
D.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
E.
religionOfConquerors
Indicates that the specified religion is practiced or upheld by the conquering group or power in a given context.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 21, 2026, 3:38 p.m.