Triple
T31120716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon (Despicable Me 2) |
E793213
|
entity |
| Predicate | importanceToMainPlot |
P26062
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Shannon (Despicable Me 2), importanceToMainPlot, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceToMainPlot Context triple: [Shannon (Despicable Me 2), importanceToMainPlot, low]
-
A.
narrativeImportance
chosen
Indicates the degree to which an entity or event is central, influential, or essential within the structure and progression of a narrative.
-
B.
dramaticImportance
Indicates that one entity holds significant narrative or emotional weight or impact in relation to another within a dramatic or storytelling context.
-
C.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
D.
majorPlotPoint
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 9:04 p.m.