Triple
T26372995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 14289 |
E660820
|
entity |
| Predicate | isIntendedForUseBy |
P160466
|
FINISHED |
| Object | accessibility evaluators |
—
|
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: accessibility evaluators | Statement: [ISO 14289, isIntendedForUseBy, accessibility evaluators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntendedForUseBy Context triple: [ISO 14289, isIntendedForUseBy, accessibility evaluators]
-
A.
isIntendedForUseBy
chosen
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
B.
isIntendedToSupport
Indicates that one entity is designed or purposed to provide assistance, reinforcement, or backing to another entity or activity.
-
C.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
D.
assessesForUseIn
Indicates that one entity evaluates another entity to determine its suitability or appropriateness for a particular use or application.
-
E.
intendedOpeningUse
Indicates that an opening (such as a door, window, or passage) is designed or meant to be used for a particular purpose or 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f610310d7c8190a14a7f7aa377846a |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:59 p.m.