Triple
T10454388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle-Vision 360° theater |
E246512
|
entity |
| Predicate | audienceOrientation |
P94133
|
FINISHED |
| Object | can look in any direction |
—
|
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: can look in any direction | Statement: [Circle-Vision 360° theater, audienceOrientation, can look in any direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceOrientation Context triple: [Circle-Vision 360° theater, audienceOrientation, can look in any direction]
-
A.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
B.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
-
E.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
- F. None of above. chosen
Provenance (4 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe47fee48190b38ec0466ff0165a |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.