Triple
T4142909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Danvers |
E89311
|
entity |
| Predicate | hasNameElement |
P3097
|
FINISHED |
| Object | Danvers |
E243611
|
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: Danvers | Statement: [South Danvers, hasNameElement, Danvers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Danvers Context triple: [South Danvers, hasNameElement, Danvers]
-
A.
Danvers, Massachusetts
chosen
Danvers, Massachusetts is a historic New England town north of Boston, best known as the former Salem Village associated with the 1692 Salem witch trials.
-
B.
Newburyport
Newburyport is a historic coastal city in northeastern Massachusetts known for its maritime heritage, preserved downtown, and role as a commuter hub to Boston.
-
C.
Swampscott
Swampscott is a coastal town in northeastern Massachusetts known for its residential character and seaside location north of Boston.
-
D.
Andover
Andover is a town in Hampshire, England, known in part for its role as a major administrative and logistical center for the British Army.
-
E.
Andover
Andover is a small rural town in northeastern Connecticut known for its lakes, forests, and residential character.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af024cc7e88190b23b39d6f5f2a2e0 |
completed | March 9, 2026, 5:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b4d712008190aa25340e1feb0804 |
completed | March 29, 2026, 5:12 a.m. |
Created at: March 9, 2026, 3:43 p.m.