Triple
T1915001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laffing Sal |
E39995
|
entity |
| Predicate | soundType |
P22084
|
FINISHED |
| Object | recorded laughter loop |
—
|
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: recorded laughter loop | Statement: [Laffing Sal, soundType, recorded laughter loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundType Context triple: [Laffing Sal, soundType, recorded laughter loop]
-
A.
soundCharacter
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
B.
hasSound
chosen
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
soundDesignBy
Indicates that the sound design for a work (such as a film, game, or performance) is created or supervised by a particular person or entity.
-
D.
speakerType
Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
-
E.
signatureSound
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.