Triple
T30301107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heldenorgel |
E770652
|
entity |
| Predicate | soundAudibleIn |
P45475
|
FINISHED |
| Object | Kufstein town center |
—
|
NE NERFINISHED |
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: Kufstein town center | Statement: [Heldenorgel, soundAudibleIn, Kufstein town center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundAudibleIn Context triple: [Heldenorgel, soundAudibleIn, Kufstein town center]
-
A.
audibleIn
chosen
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
B.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
C.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by another entity.
-
D.
auditoryIconOf
Indicates that one entity is an auditory icon that sonically represents, symbolizes, or stands in for another entity or concept.
-
E.
soundEffects
Indicates that one entity produces, contains, or is associated with sound effects used to accompany or enhance 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:48 p.m.