Triple
T21862546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbles |
E539799
|
entity |
| Predicate | hasSpeechImpairment |
P130144
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mumbles, hasSpeechImpairment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeechImpairment Context triple: [Mumbles, hasSpeechImpairment, yes]
-
A.
hasSenseImpairment
Indicates that an entity experiences a reduction or loss in one or more sensory abilities (such as sight, hearing, or touch).
-
B.
hearingImpairment
Indicates that an entity has a reduced or impaired ability to hear compared to typical auditory function.
-
C.
voiceDisorder
chosen
Indicates that an entity has a condition or impairment affecting the normal production, quality, or use of the voice.
-
D.
hasOralDiscFunction
Indicates that an entity possesses a specific functional role or capability associated with its oral disc.
-
E.
hasSpeechFluency
Indicates that an entity exhibits a certain level or quality of smoothness, coherence, and ease in spoken language production.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63beb00819092b8ec3a8ef55a39 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.