Triple
T18966155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swami Vijnanananda |
E464045
|
entity |
| Predicate | typeOfDisciple |
P38326
|
FINISHED |
| Object | sannyasin disciple of Sri Ramakrishna |
—
|
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: sannyasin disciple of Sri Ramakrishna | Statement: [Swami Vijnanananda, typeOfDisciple, sannyasin disciple of Sri Ramakrishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDisciple Context triple: [Swami Vijnanananda, typeOfDisciple, sannyasin disciple of Sri Ramakrishna]
-
A.
wasDiscipleOf
chosen
Indicates that one entity served as a disciple, student, or follower under the guidance or teaching of another entity.
-
B.
typeOfMonk
Indicates that one entity is a specific kind or category of monk in relation to another entity.
-
C.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
D.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
E.
roleInCreed
Indicates that an entity holds a specific role or function within a particular creed, doctrine, or belief system.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon