Triple
T9147230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Calder’s stabile “Elephant” |
E219486
|
entity |
| Predicate | hasIntendedViewing |
P63265
|
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: [Alexander Calder’s stabile “Elephant”, hasIntendedViewing, 360-degree viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedViewing Context triple: [Alexander Calder’s stabile “Elephant”, hasIntendedViewing, 360-degree viewing]
-
A.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
B.
intendedViewerExperience
chosen
Indicates the type or quality of experience that a piece of content is designed or expected to provide to its viewers.
-
C.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
D.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
E.
viewedBySomeAs
Indicates that at least one observer or group perceives or interprets an entity in a particular way or role.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.