Triple
T6443444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bytecode Alliance |
E138280
|
entity |
| Predicate | worksOnStandard |
P1587
|
FINISHED |
| Object | WASI |
E138279
|
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: WASI | Statement: [Bytecode Alliance, worksOnStandard, WASI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WASI Context triple: [Bytecode Alliance, worksOnStandard, WASI]
-
A.
WASI
chosen
WASI is a modular system interface designed to let WebAssembly programs safely and portably interact with operating system features like files, networking, and clocks.
-
B.
WAS
WAS is the standard three-letter abbreviation used for the Washington Commanders NFL franchise.
-
C.
WAS
WAS is the station code for Washington, D.C.’s main intercity and commuter rail hub, Union Station.
-
D.
WAS
WAS is the standard three-letter abbreviation used for the NBA team Washington Wizards.
-
E.
WES
WES is a commuter rail service in the Portland, Oregon metropolitan area that connects Beaverton and Wilsonville.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c64bc718dc8190b186d09a17562d26 |
completed | March 27, 2026, 9:20 a.m. |
Created at: March 22, 2026, 4:46 p.m.