Triple
T17692252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priscilla |
E441056
|
entity |
| Predicate | onScreenFunction |
P87539
|
FINISHED |
| Object | moving backdrop for desert landscapes |
—
|
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: moving backdrop for desert landscapes | Statement: [Priscilla, onScreenFunction, moving backdrop for desert landscapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onScreenFunction Context triple: [Priscilla, onScreenFunction, moving backdrop for desert landscapes]
-
A.
hasOnscreenFunction
chosen
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
B.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
-
C.
visualDepictionOnScreen
Indicates that one entity is visually shown or rendered on a screen as a depiction of another entity.
-
D.
onScreenLeader
Indicates that an entity serves as the primary or leading figure visibly presented on a screen in a given context or scene.
-
E.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47152306c819086d483d87348db5d |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.