Triple
T3197750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Institute of Technology Madras |
E66973
|
entity |
| Predicate | mottoInSanskrit |
P17012
|
FINISHED |
| Object | सिद्धिर्भवति कर्मजा |
—
|
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: सिद्धिर्भवति कर्मजा | Statement: [Indian Institute of Technology Madras, mottoInSanskrit, सिद्धिर्भवति कर्मजा]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoInSanskrit Context triple: [Indian Institute of Technology Madras, mottoInSanskrit, सिद्धिर्भवति कर्मजा]
-
A.
mottoTransliteration
Indicates the representation of a motto’s original text using the characters of another writing system (its transliteration).
-
B.
mottoOriginalLanguage
chosen
Indicates the language in which a motto was originally formulated or expressed.
-
C.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
E.
mottoDerivedFrom
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7192994819084817307065a25e2 |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.