Triple
T16602401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohor |
E403361
|
entity |
| Predicate | soundSourceType |
P83120
|
FINISHED |
| Object | processed acoustic sounds |
—
|
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: processed acoustic sounds | Statement: [Bohor, soundSourceType, processed acoustic sounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundSourceType Context triple: [Bohor, soundSourceType, processed acoustic sounds]
-
A.
soundCategory
Indicates the classification relationship where a sound is assigned to a particular category or type of sound.
-
B.
noiseSource
chosen
Indicates that one entity is the origin or producer of a particular noise affecting another entity or the environment.
-
C.
soundboardType
Indicates the specific category or configuration of a soundboard associated with an entity.
-
D.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
E.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d770a048190be42180b03efba0b |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.