Triple
T16310648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinberg |
E396044
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | WES |
E407396
|
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: WES | Statement: [Rheinberg, vehicleRegistrationCode, WES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WES Context triple: [Rheinberg, vehicleRegistrationCode, WES]
-
A.
WES
WES is a commuter rail service in the Portland, Oregon metropolitan area that connects Beaverton and Wilsonville.
-
B.
WES
WES is the historic Chapman code used in genealogical records to represent the former English county of Westmorland.
-
C.
WES
WES is the three-letter station code used to identify Westminster Underground Station on the London Underground network.
-
D.
WES
WES is the standard abbreviation for the Westchester Knicks, the NBA G League affiliate of the New York Knicks.
-
E.
WES
chosen
WES is the vehicle registration code used on license plates for vehicles registered in the Wesel district of Germany.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288da27f88190aa241e3addf9cd7f |
completed | April 17, 2026, 7:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001fa6ceb48190b937a15b94fd3cfa |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.