Triple
T26584141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramananda |
E667157
|
entity |
| Predicate | sampradayaFounded |
P137030
|
FINISHED |
| Object | Ramanandi Sampradaya |
—
|
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: Ramanandi Sampradaya | Statement: [Ramananda, sampradayaFounded, Ramanandi Sampradaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampradayaFounded Context triple: [Ramananda, sampradayaFounded, Ramanandi Sampradaya]
-
A.
associatedSampradaya
chosen
Indicates a relationship where one entity is linked or connected to a particular sampradaya (spiritual or religious tradition/lineage) with which it is affiliated or identified.
-
B.
BuddhistTradition
Indicates that an entity follows, embodies, or is associated with Buddhist religious, philosophical, or cultural traditions.
-
C.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
D.
foundedTemple
Indicates that an entity established or created a temple, typically as its founder.
-
E.
foundedAsTempleInYear
Indicates that an entity was originally established as a temple in a specific year.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e3b09c81908ee0b323578c6883 |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:04 a.m.