Triple
T18596446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARoS Aarhus Art Museum |
E454504
|
entity |
| Predicate | hasViewFeature |
P182
|
FINISHED |
| Object | 360-degree view of Aarhus |
—
|
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 view of Aarhus | Statement: [ARoS Aarhus Art Museum, hasViewFeature, 360-degree view of Aarhus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewFeature Context triple: [ARoS Aarhus Art Museum, hasViewFeature, 360-degree view of Aarhus]
-
A.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
E.
supportsViewThat
Indicates that one entity endorses or agrees with a particular view, opinion, or perspective held or expressed by another entity.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474ce0c08190b440cbe86b6ef7b9 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.