Triple
T23435608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilminster |
E563450
|
entity |
| Predicate | lieutenancyArea |
P2713
|
FINISHED |
| Object | Somerset |
—
|
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: Somerset | Statement: [Ilminster, lieutenancyArea, Somerset]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Somerset Context triple: [Ilminster, lieutenancyArea, Somerset]
-
A.
Somerset
chosen
Somerset is a historic county in South West England known for its rural landscapes, coastal areas, and cities such as Bath and Wells.
-
B.
Somerset
Somerset is a coastal town in Bristol County, Massachusetts, situated along the Taunton River opposite the city of Fall River.
-
C.
Somerset
Somerset is a borough in southwestern Pennsylvania that serves as the county seat of Somerset County and a gateway to the scenic Laurel Highlands region.
-
D.
Somerset
Somerset is a city in Pulaski County, Kentucky, known as a regional hub for commerce, healthcare, and recreation near Lake Cumberland.
-
E.
Somerset
Somerset is a residential neighborhood in the southwest quadrant of Calgary, Alberta, known for its family-friendly atmosphere and access to parks and amenities.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dbdf248190a09e971f2718d01f |
completed | April 29, 2026, 6:31 a.m. |
Created at: April 17, 2026, 5:50 p.m.