Triple
T5443736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sambandar |
E122196
|
entity |
| Predicate | roleInCanon |
P42552
|
FINISHED |
| Object | Tevaram primary author |
—
|
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: Tevaram primary author | Statement: [Sambandar, roleInCanon, Tevaram primary author]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCanon Context triple: [Sambandar, roleInCanon, Tevaram primary author]
-
A.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
eraInCanon
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
-
C.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
D.
fictionalUniverseRole
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
E.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.