Triple
T14276849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Nightmare Child |
E353936
|
entity |
| Predicate | visualDepictionOnScreen |
P113556
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [the Nightmare Child, visualDepictionOnScreen, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualDepictionOnScreen Context triple: [the Nightmare Child, visualDepictionOnScreen, no]
-
A.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
B.
depictsView
Indicates that one entity visually represents or portrays the view, scene, or perspective of another entity.
-
C.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
-
D.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
visualMedium
Indicates that one entity serves as the visual medium or format through which another entity is presented, communicated, or experienced.
- F. None of above. chosen
Provenance (4 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6583f0ec81909ebfc7a2c6351ff8 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.