Triple
T27166328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deewana |
E682788
|
entity |
| Predicate | introducedActor |
P5563
|
FINISHED |
| Object | Shah Rukh Khan |
—
|
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: Shah Rukh Khan | Statement: [Deewana, introducedActor, Shah Rukh Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedActor Context triple: [Deewana, introducedActor, Shah Rukh Khan]
-
A.
introducedByCharacter
Indicates that one character is responsible for presenting, bringing into the story, or otherwise causing another entity to be first revealed or made known.
-
B.
introducedByCharacters
Indicates that something (such as an idea, object, or event) is brought into the narrative or context by specific characters.
-
C.
starredActor
chosen
Indicates that an actor performed a leading or significant role in a particular production or work.
-
D.
introducedActorAsDoctor
Indicates that one entity presented or referred to an actor in the role or capacity of a doctor.
-
E.
involvedActor
Indicates that an entity participates as an actor or participant in the referenced event, activity, or situation.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 9:21 a.m.