Triple
T29159991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganzfeld experiments |
E739158
|
entity |
| Predicate | auditoryReductionMethod |
P3514
|
FINISHED |
| Object | white noise played through headphones |
—
|
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: white noise played through headphones | Statement: [Ganzfeld experiments, auditoryReductionMethod, white noise played through headphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auditoryReductionMethod Context triple: [Ganzfeld experiments, auditoryReductionMethod, white noise played through headphones]
-
A.
hearingAbility
Indicates the capacity or level to which an entity can perceive and interpret sound through hearing.
-
B.
hearingAdaptation
Indicates a change or adjustment in an entity’s hearing ability or auditory system in response to environmental or situational conditions.
-
C.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
D.
soundReproductionMethod
chosen
Indicates the method or technique used to reproduce or play back sound.
-
E.
hearingImpairment
Indicates that an entity has a reduced or impaired ability to hear compared to typical auditory function.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d0395c8190a9251c7e795ed02e |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:47 a.m.