Triple
T23795779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olvido |
E588532
|
entity |
| Predicate | involvesAudience |
P45833
|
FINISHED |
| Object | immersive participation |
—
|
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: immersive participation | Statement: [Olvido, involvesAudience, immersive participation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAudience Context triple: [Olvido, involvesAudience, immersive participation]
-
A.
attractsAudience
Indicates that an entity draws the interest or attention of people who choose to watch, listen to, or engage with it.
-
B.
engagesAudienceAs
Indicates that one entity actively captures, involves, or holds the attention of an audience in the manner or role specified by another entity.
-
C.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
D.
audienceImpact
Indicates how an action, message, or event affects, influences, or resonates with its intended audience.
-
E.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dc94d481908800385a58d2c452 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:47 p.m.