Triple
T14921725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern New Hampshire Medical Center |
E371526
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Nashua |
E75930
|
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: Nashua | Statement: [Southern New Hampshire Medical Center, city, Nashua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nashua Context triple: [Southern New Hampshire Medical Center, city, Nashua]
-
A.
Nashua, New Hampshire
chosen
Nashua, New Hampshire is a mid-sized city in southern New Hampshire known for its historic mill heritage, commercial centers, and role as part of the Greater Boston metropolitan area.
-
B.
Scituate
Scituate is a coastal town in Plymouth County, Massachusetts, known for its historic harbor, beaches, and maritime character on the state's South Shore.
-
C.
Scituate
Scituate is a rural town in central Rhode Island known for its reservoirs, woodlands, and historic New England character.
-
D.
Concord
Concord is the Roman goddess personifying harmony and agreement, especially in social and political relationships.
-
E.
Concord
Concord is a small town in Pike County, Georgia, known for its rural character and tight-knit community.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded63121e48190b54eb2546acc3c93 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e88e4a08190a56b4a1336e07bdf |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 10, 2026, 2:34 a.m.