Triple
T4806196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shefford, Bedfordshire |
E106952
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object | SG17 |
E209989
|
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: SG17 | Statement: [Shefford, Bedfordshire, hasPostcodeDistrict, SG17]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SG17 Context triple: [Shefford, Bedfordshire, hasPostcodeDistrict, SG17]
-
A.
SGC
SGC is the station code for St George's Cross, a Glasgow Subway station in Scotland.
-
B.
SGN
SGN is the IATA airport code for Tan Son Nhat International Airport, the main international gateway serving Ho Chi Minh City, Vietnam.
-
C.
SGL
SGL is the station code for Singleton railway station, a train stop serving the locality of Singleton.
-
D.
SG
chosen
SG is a postcode area in the United Kingdom covering parts of Hertfordshire and surrounding regions.
-
E.
SG
SG is the Secretariat-General of the European Commission, the central administrative body that supports the Commission’s work, coordination, and decision-making processes.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6c678e58819094cdf18d8c5ea96f |
completed | March 20, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4d9e1ea88190b098d5203bd1d145 |
completed | March 21, 2026, 7:49 a.m. |
Created at: March 20, 2026, 1:23 p.m.