Triple
T11471430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WV postcode area |
E271917
|
entity |
| Predicate | code |
P1537
|
FINISHED |
| Object | WV |
E271917
|
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: WV | Statement: [WV postcode area, code, WV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WV Context triple: [WV postcode area, code, WV]
-
A.
WV
chosen
WV is the postcode area covering Wolverhampton and surrounding parts of the West Midlands in England.
-
B.
West Virginia
West Virginia is a landlocked, mountainous U.S. state in the Appalachian region, known for its coal mining history, outdoor recreation, and distinct cultural heritage.
-
C.
WVDOH
WVDOH is the state agency responsible for planning, building, and maintaining the public road and highway system in West Virginia.
-
D.
WI
WI is the vehicle registration code used on license plates for the German city of Wiesbaden.
-
E.
N.D.W. Va.
N.D.W. Va. is the standard legal abbreviation for the United States District Court for the Northern District of West Virginia, a federal trial court within the U.S. judiciary.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d82949e3688190b024a4980666c94f |
completed | April 9, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6042507c4819096afc2839fda186d |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:35 p.m.