Triple
T12747844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldener Saal |
E304651
|
entity |
| Predicate | acousticType |
P9532
|
FINISHED |
| Object | natural acoustic |
—
|
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: natural acoustic | Statement: [Goldener Saal, acousticType, natural acoustic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acousticType Context triple: [Goldener Saal, acousticType, natural acoustic]
-
A.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
B.
acousticProperty
chosen
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
-
C.
acousticalDesigner
Indicates a relationship where one entity serves as the acoustical designer responsible for planning or shaping the sound characteristics of another entity (such as a space, product, or performance).
-
D.
soundCategory
Indicates the classification relationship where a sound is assigned to a particular category or type of sound.
-
E.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.