Triple
T33202365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanha Tanha |
E849934
|
entity |
| Predicate | featuredPerformerOnScreen |
P152890
|
FINISHED |
| Object | Urmila Matondkar |
—
|
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: Urmila Matondkar | Statement: [Tanha Tanha, featuredPerformerOnScreen, Urmila Matondkar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredPerformerOnScreen Context triple: [Tanha Tanha, featuredPerformerOnScreen, Urmila Matondkar]
-
A.
featuresOnScreenPerformer
chosen
Indicates that something (such as a work or production) includes a particular performer visibly appearing on screen.
-
B.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
-
C.
performerInShow
Indicates that an entity participates as a performer in a particular show or performance.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
featuredArtistLiveVersion
Indicates that an artist is the prominently credited performer on a live-recorded version of a work.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: May 1, 2026, 1:30 a.m.