Triple
T10561663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RG postcode area |
E249231
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object | RG7 |
E249231
|
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: RG7 | Statement: [RG postcode area, hasPostcodeDistrict, RG7]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RG7 Context triple: [RG postcode area, hasPostcodeDistrict, RG7]
-
A.
RGK
RGK is the commonly used abbreviation for the Ryukyu Golden Kings, a professional basketball team based in Okinawa, Japan.
-
B.
R37
R37 is a regional road in South Africa that serves as a key route connecting the town of Lydenburg with other parts of the Mpumalanga and Limpopo provinces.
-
C.
RGH
RGH is the IATA airport code for Balurghat Airport, a regional airport serving the town of Balurghat in West Bengal, India.
-
D.
RG
chosen
RG is a postcode area in southern England covering Reading and surrounding towns in Berkshire and parts of neighbouring counties.
-
E.
RG
RG is the former IATA airline designator for Varig, the now-defunct Brazilian flag carrier that was once the country’s largest airline.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52720621c8190a1126268ebe57c83 |
completed | April 7, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d93491d2408190b5f54afddbb51ec4 |
completed | April 10, 2026, 5:34 p.m. |
Created at: April 6, 2026, 12:35 p.m.