Triple
T25535567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamic Perspective |
E640029
|
entity |
| Predicate | enablesEffect |
P106972
|
FINISHED |
| Object | interactive depth effects |
—
|
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: interactive depth effects | Statement: [Dynamic Perspective, enablesEffect, interactive depth effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesEffect Context triple: [Dynamic Perspective, enablesEffect, interactive depth effects]
-
A.
providesEffect
chosen
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
B.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
C.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
D.
usesEffectType
Indicates that an entity employs or is associated with a particular type or category of effect in its operation or behavior.
-
E.
canonicalEffect
Indicates the standard or primary effect that an action, event, or entity is typically understood to produce.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f866376081909ab76a8aa5c3fea7 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:22 p.m.