Triple
T37680101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpfahrt (cattle ascent) |
E938202
|
entity |
| Predicate | auditoryFeature |
P48651
|
FINISHED |
| Object | ringing of large cowbells |
—
|
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: ringing of large cowbells | Statement: [Alpfahrt (cattle ascent), auditoryFeature, ringing of large cowbells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auditoryFeature Context triple: [Alpfahrt (cattle ascent), auditoryFeature, ringing of large cowbells]
-
A.
notableSoundCharacteristic
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
acousticProperty
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
-
D.
tonalFeatures
Indicates that one entity specifies or characterizes the tonal properties or qualities associated with another entity.
-
E.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa187f588190bee7e218b2ba6409 |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.