Triple
T7990995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horn Pond |
E186004
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Woburn |
E81857
|
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: Woburn | Statement: [Horn Pond, city, Woburn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Woburn Context triple: [Horn Pond, city, Woburn]
-
A.
Woburn
Woburn is a residential neighbourhood in the eastern part of Toronto, Ontario, known for its diverse community and mix of high-rise apartments and single-family homes.
-
B.
Woburn
Woburn is a historic village in Bedfordshire, England, best known for Woburn Abbey and its associated safari park and estate.
-
C.
Woburn, Massachusetts
chosen
Woburn, Massachusetts is a historic suburban city north of Boston known for its early colonial roots and later prominence in industry and commerce.
-
D.
Haverhill
Haverhill is a market town in Suffolk, England, known for its growing population, light industry, and role as a commuter hub for nearby larger cities.
-
E.
Haverhill
Haverhill is a historic city in northeastern Massachusetts that functions as a suburban community within the Greater Boston metropolitan area.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c6fc19c8190b98023e257c2f4f2 |
completed | March 31, 2026, 3:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93991e9c8190a6834b8d9fd82128 |
completed | April 1, 2026, 3:40 a.m. |
Created at: March 30, 2026, 5:16 p.m.