Triple
T22715457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windham Center Historic District |
E561719
|
entity |
| Predicate | cityOrTown |
P76028
|
FINISHED |
| Object | Windham |
—
|
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: Windham | Statement: [Windham Center Historic District, cityOrTown, Windham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Windham Context triple: [Windham Center Historic District, cityOrTown, Windham]
-
A.
Guilford
Guilford is a small village in Nodaway County, Missouri, known for its rural Midwestern character and tight-knit community.
-
B.
Guilford
Guilford is a town located within the Windham Region of Vermont, known for its rural character and New England landscape.
-
C.
Guilford
Guilford is a British territorial designation historically associated with the noble title of Baron Guilford.
-
D.
Windham, Connecticut
chosen
Windham, Connecticut is a historic town in eastern Connecticut known for its colonial-era roots and association with early American statesman Samuel Huntington.
-
E.
Fairville
Fairville is a residential neighbourhood located on the west side of Saint John, New Brunswick, Canada.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ca59881909064d49f331fb711 |
completed | April 29, 2026, 3:20 a.m. |
Created at: April 17, 2026, 3:18 p.m.