Triple
T15087834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hancock County |
E360327
|
entity |
| Predicate | hasCountySeat |
P383
|
FINISHED |
| Object | Ellsworth |
E912905
|
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: Ellsworth | Statement: [Hancock County, hasCountySeat, Ellsworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ellsworth Context triple: [Hancock County, hasCountySeat, Ellsworth]
-
A.
Ellsworth
chosen
Ellsworth is a small village located in northern Michigan, United States.
-
B.
Ellsworth
Ellsworth is a given name most notably associated with the American abstract painter and sculptor Ellsworth Kelly.
-
C.
Winslow
Winslow is the main commercial and residential hub of Bainbridge Island, Washington, known for its downtown shops, restaurants, and ferry terminal connecting to Seattle.
-
D.
Winslow
Winslow is a small historic market town in Buckinghamshire, England, known for its traditional architecture and rural surroundings.
-
E.
Winslow
Winslow is an English-origin surname historically associated with early colonial families in New England.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae1ba4208190b1e8c55668a1b422 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:03 a.m.