Triple
T193027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WAI-ARIA |
E3759
|
entity |
| Predicate | bestPractice |
P488
|
FINISHED |
| Object | use native HTML semantics before ARIA |
—
|
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: use native HTML semantics before ARIA | Statement: [WAI-ARIA, bestPractice, use native HTML semantics before ARIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestPractice Context triple: [WAI-ARIA, bestPractice, use native HTML semantics before ARIA]
-
A.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
B.
hasImportantPractice
Indicates that an entity engages in or possesses a practice, activity, or procedure considered significant or essential within a given context.
-
C.
advises
chosen
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
D.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
E.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a256769ad8819083c1d83082c0215e |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.