Triple
T3397784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony Hall |
E71570
|
entity |
| Predicate | hasAdjustableAcoustics |
P9532
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Symphony Hall, hasAdjustableAcoustics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjustableAcoustics Context triple: [Symphony Hall, hasAdjustableAcoustics, yes]
-
A.
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).
-
B.
acousticProperty
chosen
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
-
C.
hasLFEChannels
Indicates that an entity includes or is associated with one or more Low-Frequency Effects (LFE) audio channels.
-
D.
hasAmbience
Indicates that one entity provides or is characterized by a particular atmosphere, mood, or environmental quality experienced in or around another entity.
-
E.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c4099081908a236376b4f86900 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.