Triple
T10698359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Massachusetts |
E252203
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Littleton |
E2879
|
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: Littleton | Statement: [Northern Massachusetts, hasTown, Littleton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Littleton Context triple: [Northern Massachusetts, hasTown, Littleton]
-
A.
Littleton
chosen
Littleton is a suburban town in Middlesex County, Massachusetts, located northwest of Boston.
-
B.
Littleton
Littleton is a village in Surrey, England, known for its proximity to Shepperton and its largely residential, semi-rural character.
-
C.
Littleton, Colorado
Littleton, Colorado is a suburban city in the Denver metropolitan area known for its historic downtown, residential neighborhoods, and proximity to the South Platte River.
-
D.
Broomfield
Broomfield is a village and civil parish in Essex, England, situated just north of the city of Chelmsford.
-
E.
Broomfield
Broomfield is a consolidated city and county in north-central Colorado, known for its suburban communities, tech employers, and location between Denver and Boulder along the Front Range.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8a03848190bf68dd470bee103a |
completed | April 9, 2026, 1:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff777c63c8190a989d33e8460bc2f |
completed | April 15, 2026, 8:39 p.m. |
Created at: April 8, 2026, 9:12 p.m.