Triple
T15811982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BS postcode area |
E383375
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object | BS39 |
E707812
|
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: BS39 | Statement: [BS postcode area, hasPostcodeDistrict, BS39]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BS39 Context triple: [BS postcode area, hasPostcodeDistrict, BS39]
-
A.
BS39
chosen
BS39 is a UK postcode district in the Bristol area covering Bishop Sutton and surrounding parts of North East Somerset.
-
B.
BS40
BS40 is a UK postcode district in the Bristol area covering Blagdon and surrounding parts of North Somerset.
-
C.
B39M
B39M is the ICAO aircraft type designator used to identify the Boeing 737 MAX 9 variant in aviation operations and documentation.
-
D.
BS11
BS11 is a Japanese satellite television channel known for broadcasting anime and other entertainment programming nationwide.
-
E.
B33
B33 is the catalog designation for the Horsehead Nebula, a dark molecular cloud in the constellation Orion whose distinctive silhouette resembles a horse’s head.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52bbb888190b226567e84ced7e9 |
completed | April 16, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9993c86c8190b1d106af7537080a |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:49 a.m.