Triple
T32244367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Temple |
E823705
|
entity |
| Predicate | hasOnScreenDeath |
P180738
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Harry Temple, hasOnScreenDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenDeath Context triple: [Harry Temple, hasOnScreenDeath, true]
-
A.
hasOnScreenDestruction
Indicates that something is depicted being damaged, ruined, or destroyed within the visible content (e.g., on screen or in the scene).
-
B.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
-
C.
hasOnScreenResidence
Indicates that an entity has a residence or home that is depicted or shown on screen within a visual work.
-
D.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
E.
hasOnScreenOccupation
Indicates that an entity is depicted as having a particular occupation or job within an on-screen context (e.g., in a film, TV show, or other visual media).
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: May 1, 2026, 12:40 a.m.