Triple
T25238917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shree 420 |
E632410
|
entity |
| Predicate | featuresIconicScene |
P110949
|
FINISHED |
| Object | umbrella scene in Pyar Hua Ikrar Hua |
—
|
LITERAL FINISHED |
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: umbrella scene in Pyar Hua Ikrar Hua | Statement: [Shree 420, featuresIconicScene, umbrella scene in Pyar Hua Ikrar Hua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresIconicScene Context triple: [Shree 420, featuresIconicScene, umbrella scene in Pyar Hua Ikrar Hua]
-
A.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
B.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
C.
featuresSceneFrom
chosen
Indicates that one entity (such as a work or media item) includes or presents a particular scene taken from another entity.
-
D.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
E.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 1:07 p.m.