Triple
T6034379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immersive Reader |
E134380
|
entity |
| Predicate | supportsAccessibilityNeed |
P48626
|
FINISHED |
| Object | visual impairments |
—
|
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: visual impairments | Statement: [Immersive Reader, supportsAccessibilityNeed, visual impairments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessibilityNeed Context triple: [Immersive Reader, supportsAccessibilityNeed, visual impairments]
-
A.
providesAccessibility
chosen
Indicates that one entity enables or improves access to another entity, resource, or service, removing or reducing barriers to its use.
-
B.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
recognizedNeedFor
Indicates that one entity has identified or acknowledged the necessity or requirement for another entity or condition.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b33a7c8190ad6282286199b192 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.