Triple
T1833369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk |
E41008
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Cromer |
E169084
|
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: Cromer | Statement: [Norfolk, contains, Cromer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cromer Context triple: [Norfolk, contains, Cromer]
-
A.
Cromer
chosen
Cromer is a traditional seaside town on the north coast of Norfolk, England, known for its Victorian pier, sandy beaches, and famous Cromer crab.
-
B.
Great Yarmouth
Great Yarmouth is a coastal town and seaside resort in Norfolk, England, historically significant as a fishing port and parliamentary borough.
-
C.
Hartlepool
Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
-
D.
Clacton-on-Sea
Clacton-on-Sea is a seaside resort town on the Essex coast of England, known for its sandy beaches, pier, and traditional British holiday attractions.
-
E.
Skegness
Skegness is a seaside town and popular holiday resort on the east coast of England.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb02540dc819081b19a09562139cd |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3c39a448190923588d9c07313e1 |
completed | March 8, 2026, 10:10 p.m. |
Created at: March 4, 2026, 7:33 p.m.