Triple
T29299710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozhi |
E742925
|
entity |
| Predicate | leadPair |
P166821
|
FINISHED |
| Object | Prithviraj Sukumaran and Jyothika |
—
|
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: Prithviraj Sukumaran and Jyothika | Statement: [Mozhi, leadPair, Prithviraj Sukumaran and Jyothika]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadPair Context triple: [Mozhi, leadPair, Prithviraj Sukumaran and Jyothika]
-
A.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
B.
leadCallAndResponsePartner
Indicates a relationship where one entity initiates a call-and-response interaction and the other serves as its primary responding partner.
-
C.
leadSingleFrom
Indicates that one entity serves as the lead single taken from another entity, typically a larger work such as an album or release.
-
D.
leadUnionFigure
Indicates that an entity serves as a primary or prominent leader within a labor union or union-related movement.
-
E.
leadSingleFeaturing
Indicates that an artist is featured on the lead single of another artist’s release.
- F. None of above. chosen
Provenance (4 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a1a7148190ae6060514d16ffec |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:09 p.m.