Triple
T25701392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stardust Memories |
E644471
|
entity |
| Predicate | hasMiseEnSceneInfluence |
P41012
|
FINISHED |
| Object | Federico Fellini |
—
|
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: Federico Fellini | Statement: [Stardust Memories, hasMiseEnSceneInfluence, Federico Fellini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiseEnSceneInfluence Context triple: [Stardust Memories, hasMiseEnSceneInfluence, Federico Fellini]
-
A.
hasInfluenceFromScene
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
B.
hasCinematicFeature
Indicates that something possesses a specific cinematic characteristic, quality, or element related to film or visual storytelling.
-
C.
hasFilmStyle
chosen
Indicates that a film exhibits or is characterized by a particular cinematic style or aesthetic approach.
-
D.
performedInScene
Indicates that an action or event took place within a specific scene or setting.
-
E.
metacinematicElement
Indicates that one element in a work refers to, comments on, or foregrounds the nature, techniques, or conventions of cinema or filmmaking itself.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 8:46 p.m.