Triple
T19950728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedbergh |
E479545
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | SEDBERGH |
—
|
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: SEDBERGH | Statement: [Sedbergh, hasPostTown, SEDBERGH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEDBERGH Context triple: [Sedbergh, hasPostTown, SEDBERGH]
-
A.
SEDBERGH
chosen
Sedbergh is a small market town in Cumbria, England, known for its historic buildings, surrounding Howgill Fells, and reputation as England’s official book town.
-
B.
Seeberg
Seeberg is a small Swiss municipality located in the Emmental region of the canton of Bern.
-
C.
Seeberg
Seeberg is a German-language surname associated with various notable individuals, including theologian Reinhold Seeberg.
-
D.
Sundsberg
Sundsberg is a residential village and district in the municipality of Kirkkonummi in southern Finland, known for its modern housing and proximity to the Helsinki metropolitan area.
-
E.
Smedby
Smedby is a residential locality in Sweden situated within Upplands Väsby Municipality, north of Stockholm.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6b694c819080daea9422bcdd38 |
completed | April 20, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:54 p.m.