Triple
T10454358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle-Vision 360° theater |
E246512
|
entity |
| Predicate | projectionAngle |
P94132
|
FINISHED |
| Object | 360 degrees |
—
|
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 degrees | Statement: [Circle-Vision 360° theater, projectionAngle, 360 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectionAngle Context triple: [Circle-Vision 360° theater, projectionAngle, 360 degrees]
-
A.
depictionAngle
Indicates the angle or viewpoint from which something is visually depicted or represented.
-
B.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
C.
offAxisAngle
Indicates the angle by which something is rotated or deviates from a defined primary or reference axis.
-
D.
pyramidAngle
Indicates that there is a specified angular relationship between elements (such as faces, edges, or apex and base) of a pyramid-shaped structure.
-
E.
angleProperty
Indicates that a relationship specifies a particular geometric or quantitative characteristic (such as measure, type, or orientation) of an angle between entities.
- 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.