Triple
T7430953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramanandi Sampradaya |
E171485
|
entity |
| Predicate | spread |
P9468
|
FINISHED |
| Object | primarily North India |
—
|
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: primarily North India | Statement: [Ramanandi Sampradaya, spread, primarily North India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spread Context triple: [Ramanandi Sampradaya, spread, primarily North India]
-
A.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
B.
spreadTo
chosen
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
-
C.
share
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
-
D.
spreadingStatus
Indicates the current state or progression of how something is spreading or being disseminated (e.g., whether and how it is expanding, stable, or declining).
-
E.
dispersion
Indicates the degree to which items in a set are spread out or scattered relative to one another.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f324afac8190b34fcac95fd57410 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.