Triple
T21151434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWV 49 |
E521197
|
entity |
| Predicate | usesArias |
P63471
|
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: [LWV 49, usesArias, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArias Context triple: [LWV 49, usesArias, yes]
-
A.
hasAria
chosen
Indicates that one entity possesses, contains, or is associated with an aria (a specific vocal piece or melodic section).
-
B.
hasARIAcertification
Indicates that an entity possesses an ARIA (Accessible Rich Internet Applications) certification attesting to compliance with relevant accessibility standards.
-
C.
supportsAAC
Indicates that one entity provides compatibility with, or functional support for, AAC (Augmentative and Alternative Communication) methods or technologies for another entity.
-
D.
accessibilityFeatures
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
-
E.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.