Triple
T26036657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruppavai |
E647568
|
entity |
| Predicate | didacticUse |
P63933
|
FINISHED |
| Object | taught to children in Tamil Vaishnava families |
—
|
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: taught to children in Tamil Vaishnava families | Statement: [Tiruppavai, didacticUse, taught to children in Tamil Vaishnava families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didacticUse Context triple: [Tiruppavai, didacticUse, taught to children in Tamil Vaishnava families]
-
A.
didacticPurpose
Indicates that something is intended to teach, instruct, or convey educational content or guidance.
-
B.
didacticCharacter
Indicates that one entity serves a teaching or instructional role toward another, conveying guidance, lessons, or moral instruction.
-
C.
educationUse
Indicates the use or application of something specifically for educational purposes or in an educational context.
-
D.
usesInTeaching
chosen
Indicates that an agent employs a particular resource, method, or material as part of their teaching activities.
-
E.
usedInEducationIn
Indicates that something is employed or applied within educational contexts in a particular place or institution.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061e95848190b6a47fd49280ad1c |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:08 a.m.