Triple
T7361966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WR postcode area |
E169771
|
entity |
| Predicate | postcodeAreaCode |
P920
|
FINISHED |
| Object | WR |
E169771
|
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: WR | Statement: [WR postcode area, postcodeAreaCode, WR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WR Context triple: [WR postcode area, postcodeAreaCode, WR]
-
A.
WR
WR is the abbreviation for the German Council of Science and Humanities, a key advisory body that counsels the German federal and state governments on science, research, and higher education policy.
-
B.
WR
chosen
WR is the postcode area designation covering Worcester and surrounding parts of Worcestershire in England.
-
C.
WR
WR is the standard abbreviation for World Rugby, the international governing body for the sport of rugby union.
-
D.
WR
WR is the official abbreviation for the Western Railway zone of Indian Railways, which operates major rail services across western India.
-
E.
WR
WR is the vehicle registration code assigned to the city of Radom in Poland.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f15e0280819086627cef15fe18bd |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fab3a9d88190b9193dd0729eba5a |
completed | March 28, 2026, 3:58 p.m. |
Created at: March 27, 2026, 3:06 p.m.