Triple
T27279244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himanshu Rai |
E688284
|
entity |
| Predicate | partnerInFilmCompany |
P123417
|
FINISHED |
| Object | Devika Rani |
—
|
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: Devika Rani | Statement: [Himanshu Rai, partnerInFilmCompany, Devika Rani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInFilmCompany Context triple: [Himanshu Rai, partnerInFilmCompany, Devika Rani]
-
A.
partnerInProductionCompanyWith
chosen
Indicates that two entities are business partners together in operating or owning the same production company.
-
B.
businessPartnerInFilm
Indicates that two entities are business partners within the context of a specific film or film-related project.
-
C.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
D.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
E.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:05 a.m.