Triple
T8549943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhavi |
E202419
|
entity |
| Predicate | roleInManimekalai |
P42552
|
FINISHED |
| Object | mother of the heroine Manimekalai |
—
|
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: mother of the heroine Manimekalai | Statement: [Madhavi, roleInManimekalai, mother of the heroine Manimekalai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInManimekalai Context triple: [Madhavi, roleInManimekalai, mother of the heroine Manimekalai]
-
A.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
-
C.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
D.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe75589d8819096177ddbd3dafcb6 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.