Triple
T25454119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madan Mohan |
E637866
|
entity |
| Predicate | posthumousCollaborationWith |
P72222
|
FINISHED |
| Object | Yash Chopra |
—
|
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: Yash Chopra | Statement: [Madan Mohan, posthumousCollaborationWith, Yash Chopra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousCollaborationWith Context triple: [Madan Mohan, posthumousCollaborationWith, Yash Chopra]
-
A.
posthumousWorkUsedIn
Indicates that a work created or published after a creator’s death is utilized, referenced, or incorporated within another work or context.
-
B.
hasPosthumousRelease
Indicates that a work was released or made publicly available only after its creator’s death.
-
C.
posthumouslyEditedBy
Indicates that a work was edited by the specified agent after its creator or original author had died.
-
D.
posthumousAssociation
chosen
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
-
E.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f723c0688190ada84606ce6be35b |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:04 p.m.