Triple
T367157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATAG |
E7986
|
entity |
| Predicate | developedBy |
P73
|
FINISHED |
| Object | WAI |
E1920
|
NE 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: WAI | Statement: [ATAG, developedBy, WAI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WAI Context triple: [ATAG, developedBy, WAI]
-
A.
WAI
chosen
WAI (Web Accessibility Initiative) is a World Wide Web Consortium (W3C) program that develops guidelines, resources, and standards to make the web accessible to people with disabilities.
-
B.
WAI-ARIA
WAI-ARIA is a technical specification that defines ways to make web content and applications more accessible to people with disabilities by providing semantic information to assistive technologies.
-
C.
WAS
WAS is the standard three-letter abbreviation used for the Washington Commanders NFL franchise.
-
D.
WAS
WAS is the station code for Washington, D.C.’s main intercity and commuter rail hub, Union Station.
-
E.
WAS
WAS is the standard three-letter abbreviation used for the NBA team Washington Wizards.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3ecaaf780819081db5cfbe8af0894 |
completed | March 1, 2026, 7:37 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.