Triple
T35960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Nationals |
E712
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | WSH |
E1380
|
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: WSH | Statement: [Washington Nationals, abbreviation, WSH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WSH Context triple: [Washington Nationals, abbreviation, WSH]
-
A.
WSH
chosen
WSH is the standard sports abbreviation for the Washington Commanders, the National Football League team based in the Washington, D.C. area.
-
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.
W3
W3 is a common shorthand for the World Wide Web, the global system of interlinked hypertext documents and resources accessed via the internet.
-
E.
WAI
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.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24aca5ed481908d1aa2ca656f25ea |
completed | Feb. 28, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a255322d048190b3a45c6c6a80230c |
completed | Feb. 28, 2026, 2:38 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.