Triple
T23432240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nivruttinath |
E563362
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Sopan |
—
|
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: Sopan | Statement: [Nivruttinath, sibling, Sopan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sopan Context triple: [Nivruttinath, sibling, Sopan]
-
A.
Sopandev
chosen
Sopandev was a revered medieval Marathi saint and poet of the Varkari tradition, known for his devotional compositions and spiritual influence in Maharashtra.
-
B.
Sudharak
Sudharak was a Marathi-language social reformist periodical associated with progressive thinker Gopal Ganesh Agarkar, known for advocating rationalism and social change in late 19th-century India.
-
C.
Sankar
Sankar is a common Indian given name and surname, often associated with Hindu cultural and religious traditions.
-
D.
Surada
Surada is a town in the Ganjam district of the Indian state of Odisha, known as a local commercial and administrative center for surrounding rural areas.
-
E.
Sudarshan
Sudarshan is a common Indian surname found across various regions and communities in India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d920548190904f80c7c40cba06 |
completed | April 29, 2026, 6:31 a.m. |
Created at: April 17, 2026, 5:49 p.m.