Triple
T36784126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laura Dern as Diana |
E908853
|
entity |
| Predicate | hasOnScreenParents |
P141370
|
FINISHED |
| Object | Diana’s parents (unnamed characters) |
—
|
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: Diana’s parents (unnamed characters) | Statement: [Laura Dern as Diana, hasOnScreenParents, Diana’s parents (unnamed characters)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenParents Context triple: [Laura Dern as Diana, hasOnScreenParents, Diana’s parents (unnamed characters)]
-
A.
hasOnScreenRelative
chosen
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
-
B.
onScreenSibling
Indicates that two characters are depicted as siblings within an on-screen or fictional context.
-
C.
hasOnScreenOwner
Indicates that an entity is owned or controlled by another entity that is explicitly shown or represented on screen.
-
D.
hasOnScreenLocationType
Indicates that an entity’s location, as presented or visible on a screen, is of a specified type or category.
-
E.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.