Triple
T26125171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahma Sampradaya |
E659079
|
entity |
| Predicate | transmissionLineageFrom |
P115355
|
FINISHED |
| Object | Vishnu to Brahma |
—
|
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: Vishnu to Brahma | Statement: [Brahma Sampradaya, transmissionLineageFrom, Vishnu to Brahma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionLineageFrom Context triple: [Brahma Sampradaya, transmissionLineageFrom, Vishnu to Brahma]
-
A.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
B.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
C.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
D.
titleLineageStart
Indicates the point in time or event at which a particular title or rank first begins within a lineage or succession.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 26, 2026, 8:11 p.m.