Triple
T29334176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sachaa Jhutha |
E743864
|
entity |
| Predicate | featuresDoubleRoleBy |
P192492
|
FINISHED |
| Object | Rajesh Khanna |
—
|
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: Rajesh Khanna | Statement: [Sachaa Jhutha, featuresDoubleRoleBy, Rajesh Khanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDoubleRoleBy Context triple: [Sachaa Jhutha, featuresDoubleRoleBy, Rajesh Khanna]
-
A.
featuresDoubleAct
Indicates that an entity includes or presents a performance, show, or act involving two main performers acting together as a pair.
-
B.
featuresDualRole
Indicates that an entity simultaneously fulfills two distinct roles or functions within a given context.
-
C.
portraysDoubleRole
chosen
Indicates that a single performer or entity depicts or assumes two distinct roles within the same context or work.
-
D.
bilateralRole
Indicates a relationship where each of two entities holds a defined role with respect to the other in a mutual or two-sided interaction.
-
E.
combinesRoleOf
Indicates a relationship where a single entity simultaneously fulfills or merges multiple distinct roles or functions.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 28, 2026, 1:30 p.m.