Triple
T1377443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine |
E29256
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bangor |
E18442
|
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: Bangor | Statement: [Maine, contains, Bangor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bangor Context triple: [Maine, contains, Bangor]
-
A.
Bangor metropolitan area
The Bangor metropolitan area is a regional urban and economic hub in central-eastern Maine centered on the city of Bangor and its surrounding communities.
-
B.
Bangor, Maine
chosen
Bangor, Maine is a small city in eastern Maine known as a regional commercial and cultural hub and famously associated with author Stephen King.
-
C.
Colchester
Colchester is a historic town in Essex, England, often cited as Britain’s oldest recorded town and known for its Roman heritage and medieval landmarks.
-
D.
Falmouth
Falmouth is a prominent coastal town on Cape Cod in Massachusetts known for its beaches, ferry access to Martha’s Vineyard, and historic New England charm.
-
E.
Gilford
Gilford is a small lakeside community within the town of Innisfil in Simcoe County, Ontario, Canada.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acd488698481909411c004aadfcaec |
completed | March 8, 2026, 1:44 a.m. |
Created at: March 1, 2026, 7:59 p.m.