Triple
T31239322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ParaNorman |
E796512
|
entity |
| Predicate | hasUndeadElements |
P13814
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ParaNorman, hasUndeadElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndeadElements Context triple: [ParaNorman, hasUndeadElements, yes]
-
A.
isUndead
Indicates that an entity is no longer living in a natural sense but continues to exist through supernatural or unnatural means.
-
B.
hasAfterlifeElement
Indicates that something includes, depicts, or is associated with an element related to an afterlife or post-mortem existence.
-
C.
hasSurvivalElements
Indicates that something includes features or conditions related to survival, such as resource management, threat avoidance, or sustaining life over time.
-
D.
hasSurrealElements
Indicates that something contains dreamlike, bizarre, or illogical features that depart from ordinary reality.
-
E.
containsSupernaturalElement
chosen
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:11 p.m.