Triple
T12843183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dean Court |
E307105
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Bournemouth |
E38127
|
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: Bournemouth | Statement: [Dean Court, locatedIn, Bournemouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bournemouth Context triple: [Dean Court, locatedIn, Bournemouth]
-
A.
Bournemouth
chosen
Bournemouth is a large coastal resort town on England’s south coast, known for its sandy beaches, tourism, and role as a regional commercial and transport hub.
-
B.
Poole
Poole is a coastal town and seaport in Dorset, England, known for its large natural harbour and maritime activities.
-
C.
Bristol
Bristol is a city in central Connecticut known for being the home of ESPN and for its historic clock-making industry.
-
D.
Bristol
Bristol is a city in central Connecticut known historically for its clock-making industry and as the longtime home of ESPN’s headquarters.
-
E.
Bristol
Bristol is a small town located in Dane County in the U.S. state of Wisconsin.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff3a7208190b93f6292ed5efc07 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbb93c688190910ffb6bc6fbef3f |
completed | May 3, 2026, 4:14 a.m. |
Created at: April 9, 2026, 5:35 p.m.