Triple
T20010194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billingham |
E494568
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | BILLINGHAM |
—
|
NE NERFINISHED |
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: BILLINGHAM | Statement: [Billingham, postTown, BILLINGHAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BILLINGHAM Context triple: [Billingham, postTown, BILLINGHAM]
-
A.
Billingham
chosen
Billingham is an industrial town in County Durham, England, known historically for its chemical industry and proximity to the River Tees.
-
B.
Berwick
Berwick is a small town in Nova Scotia, Canada, known for its location in the agricultural Annapolis Valley and its apple-growing heritage.
-
C.
Berwick
Berwick is a small borough in northeastern Pennsylvania known historically for its manufacturing industry and annual Halloween parade.
-
D.
Blyth
Blyth is a small historic village and civil parish in the Bassetlaw district of Nottinghamshire, England.
-
E.
Blyth
Blyth is a coastal town and port in southeast Northumberland, England, known historically for coal mining and shipbuilding.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a81c5881909692fcaaf59a57c9 |
completed | April 20, 2026, 5:26 p.m. |
Created at: April 11, 2026, 3:33 p.m.