Triple
T29301585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raa Raa Ramaiya |
E742973
|
entity |
| Predicate | hasPicturizationActor |
P37076
|
FINISHED |
| Object | Rajinikanth |
—
|
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: Rajinikanth | Statement: [Raa Raa Ramaiya, hasPicturizationActor, Rajinikanth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPicturizationActor Context triple: [Raa Raa Ramaiya, hasPicturizationActor, Rajinikanth]
-
A.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
-
B.
hasIconographicFigure
chosen
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
C.
isProgrammaticDepictionOf
Indicates that one entity is a programmatically generated or computational representation of another entity.
-
D.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
E.
hasIllustrativeElement
Indicates that one entity includes, contains, or is associated with a visual or illustrative component that helps depict, explain, or exemplify it.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 1:10 p.m.