Triple
T19137776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lulu (opera production) |
E468476
|
entity |
| Predicate | hasMultimediaElement |
P7961
|
FINISHED |
| Object | film projection |
—
|
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: film projection | Statement: [Lulu (opera production), hasMultimediaElement, film projection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultimediaElement Context triple: [Lulu (opera production), hasMultimediaElement, film projection]
-
A.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
B.
hasMediatizedStatus
Indicates that an entity holds a status or condition that has been shaped, transformed, or influenced through media processes or representations.
-
C.
hasMediaPlayer
Indicates that an entity is equipped with or associated with a media player capable of playing audio or video content.
-
D.
hasAssociatedMedium
chosen
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
E.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ee8b988190914ef21ca1b890c6 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.