Triple
T29986611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calc |
E761749
|
entity |
| Predicate | hasFeatureForAccessibility |
P80912
|
FINISHED |
| Object | Assistive technology support |
—
|
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: Assistive technology support | Statement: [Calc, hasFeatureForAccessibility, Assistive technology support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureForAccessibility Context triple: [Calc, hasFeatureForAccessibility, Assistive technology support]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasAccessibilityVariation
Indicates that one entity differs from another in terms of accessibility features, conditions, or support.
-
C.
accessibilityFeatures
chosen
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
-
D.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
-
E.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 6:36 p.m.