Triple
T30118488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Rippon |
E765490
|
entity |
| Predicate | hasHearingImpairment |
P35501
|
FINISHED |
| Object | was born with severe hearing loss |
—
|
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: was born with severe hearing loss | Statement: [Adam Rippon, hasHearingImpairment, was born with severe hearing loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHearingImpairment Context triple: [Adam Rippon, hasHearingImpairment, was born with severe hearing loss]
-
A.
hearingImpairment
chosen
Indicates that an entity has a reduced or impaired ability to hear compared to typical auditory function.
-
B.
hearingAbility
Indicates the capacity or level to which an entity can perceive and interpret sound through hearing.
-
C.
hearingType
Indicates the type or category of a hearing event or proceeding that takes place.
-
D.
hasSenseImpairment
Indicates that an entity experiences a reduction or loss in one or more sensory abilities (such as sight, hearing, or touch).
-
E.
hearingTreatment
Indicates a treatment or intervention applied to improve, restore, or manage an entity’s hearing ability.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:12 p.m.