Triple
T26150106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabbar Singh |
E659790
|
entity |
| Predicate | characterPlayedByPawanKalyan |
P9616
|
FINISHED |
| Object | Gabbar Singh |
—
|
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: Gabbar Singh | Statement: [Gabbar Singh, characterPlayedByPawanKalyan, Gabbar Singh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterPlayedByPawanKalyan Context triple: [Gabbar Singh, characterPlayedByPawanKalyan, Gabbar Singh]
-
A.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
C.
portraysInVikramarjunaVijaya
Indicates that one entity depicts or represents another within the context of the work "Vikramarjuna Vijaya."
-
D.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
E.
hasPortrayedPersonRole
Indicates that an entity has performed or held a specific role in portraying a particular person (e.g., in a film, play, or other representation).
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 26, 2026, 8:24 p.m.