Triple
T7855375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnham-on-Crouch |
E182161
|
entity |
| Predicate | postcodeArea |
P920
|
FINISHED |
| Object | CM |
E286818
|
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: CM | Statement: [Burnham-on-Crouch, postcodeArea, CM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CM Context triple: [Burnham-on-Crouch, postcodeArea, CM]
-
A.
CM
CM is the post-nominal letters used to denote a Member of the Order of Canada, one of the country’s highest civilian honors.
-
B.
CM
CM is the two-letter ISO 3166-1 alpha-2 country code assigned to Cameroon.
-
C.
CM
CM is the commonly used abbreviation for the Committee of Ministers, the decision-making body of the Council of Europe composed of the foreign ministers of member states or their representatives.
-
D.
CM
chosen
CM is the postcode area in the United Kingdom that covers Chelmsford and surrounding parts of Essex.
-
E.
CM
CM is the stock ticker symbol for the Canadian Imperial Bank of Commerce, one of Canada's largest and oldest chartered banks.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a74592c8190b42f298e3e33617b |
completed | March 31, 2026, 12:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b27e9b081909a0574458ddf43b0 |
completed | March 31, 2026, 5:27 a.m. |
Created at: March 30, 2026, 4:52 p.m.