Triple
T16000560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham Coast Line |
E388079
|
entity |
| Predicate | connectsTown |
P845
|
FINISHED |
| Object | Horden |
E748583
|
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: Horden | Statement: [Durham Coast Line, connectsTown, Horden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horden Context triple: [Durham Coast Line, connectsTown, Horden]
-
A.
Horden
chosen
Horden is a coastal village in County Durham, England, historically known for its coal mining community and proximity to the town of Peterlee.
-
B.
Aldrington
Aldrington is a residential area and former village that now forms a western suburb of Hove on the south coast of England.
-
C.
Hakeburg
Hakeburg is a historic castle-like manor and former research facility located in Kleinmachnow, Germany.
-
D.
Sebergham
Sebergham is a rural village and civil parish in Cumbria, England, known for its scenic countryside and historic character.
-
E.
Hawise
Hawise is a medieval European female given name borne by several noblewomen in England and France.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157fba9748190ac8fc27b167d49f7 |
completed | April 16, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3d99ca08190a3d07a0802b1b24a |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:55 a.m.