Triple
T5468036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundarar |
E122760
|
entity |
| Predicate | hasDisciplesAndFollowers |
P59786
|
FINISHED |
| Object | Shaivite devotees |
—
|
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: Shaivite devotees | Statement: [Sundarar, hasDisciplesAndFollowers, Shaivite devotees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisciplesAndFollowers Context triple: [Sundarar, hasDisciplesAndFollowers, Shaivite devotees]
-
A.
hasDisciplesAndFollowersTradition
Indicates that an entity has an associated tradition concerning its disciples and followers, including how they are understood, organized, or transmitted over time.
-
B.
wasDiscipleOf
Indicates that one entity served as a disciple, student, or follower under the guidance or teaching of another entity.
-
C.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
D.
laterAdherentsCount
Indicates the number of adherents who joined or adopted something after an initial reference point or time.
-
E.
hasFollowers
chosen
Indicates that an entity is followed or subscribed to by one or more other entities.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.