Triple
T18023892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stinson band organ |
E431196
|
entity |
| Predicate | soundLevel |
P32166
|
FINISHED |
| Object | sufficient to be heard across a midway |
—
|
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: sufficient to be heard across a midway | Statement: [Stinson band organ, soundLevel, sufficient to be heard across a midway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundLevel Context triple: [Stinson band organ, soundLevel, sufficient to be heard across a midway]
-
A.
noiseLevel
chosen
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
B.
soundHeardDistanceApproximate
Indicates that a sound was heard at an estimated, not precisely measured, distance from the listener or reference point.
-
C.
volumeLevels
Indicates the relative loudness or intensity settings assigned to one or more entities or audio outputs.
-
D.
soundAmplification
Indicates that one entity increases the loudness or intensity of another entity’s sound.
-
E.
hasSpeechLevels
Indicates that a language, dialect, or communicative system distinguishes different levels or styles of speech used according to social context, formality, or relative status between speakers.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c475dc819086c4cd86d663791f |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.