Triple
T21772858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamadagni |
E537478
|
entity |
| Predicate | ashramTraditionallyLocatedAt |
P136085
|
FINISHED |
| Object | banks of the Narmada River |
—
|
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: banks of the Narmada River | Statement: [Jamadagni, ashramTraditionallyLocatedAt, banks of the Narmada River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ashramTraditionallyLocatedAt Context triple: [Jamadagni, ashramTraditionallyLocatedAt, banks of the Narmada River]
-
A.
hasAshramaAt
chosen
Indicates that an ashrama (hermitage or spiritual retreat) is located at or associated with a specific place.
-
B.
ashramEstablishedFor
Indicates that an ashram was founded or set up specifically for the benefit, use, or purpose of a particular person, group, or cause.
-
C.
wasGuruResidenceOf
Indicates that a particular place served as the residence of a specific guru.
-
D.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
-
E.
spiritualCenterOf
Indicates that one entity serves as the primary locus or focal point of spiritual life, practice, or significance for another entity or group.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031af6a488190a2dcebed43d199d4 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.