Triple
T2219412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Rêve – The Dream |
E48104
|
entity |
| Predicate | audienceExperience |
P29388
|
FINISHED |
| Object | 360-degree viewing |
—
|
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: 360-degree viewing | Statement: [Le Rêve – The Dream, audienceExperience, 360-degree viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceExperience Context triple: [Le Rêve – The Dream, audienceExperience, 360-degree viewing]
-
A.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
B.
fanExperienceFeature
chosen
Indicates a feature or aspect specifically designed to shape, enhance, or characterize a fan’s overall experience.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
E.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.