Triple
T29212870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jailer |
E740587
|
entity |
| Predicate | leadActorForCharacter Tiger Muthuvel Pandian |
P166850
|
FINISHED |
| Object | Rajinikanth |
—
|
NE NERFINISHED |
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: Rajinikanth | Statement: [Jailer, leadActorForCharacter Tiger Muthuvel Pandian, Rajinikanth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacter Tiger Muthuvel Pandian Context triple: [Jailer, leadActorForCharacter Tiger Muthuvel Pandian, Rajinikanth]
-
A.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
B.
actorForCharacterThenmozhi
Indicates that an entity serves as the actor portraying the character Thenmozhi.
-
C.
leadRoleActor
chosen
Indicates that an actor performs a leading or principal role in a work or production.
-
D.
directorCharacterName
Indicates that the specified name is the character name used by the director (or representing the director) within a work.
-
E.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:12 p.m.