Triple
T2235641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford, Maine |
E49272
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Poland, Maine |
E64413
|
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: Poland, Maine | Statement: [Oxford, Maine, adjacentTo, Poland, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poland, Maine Context triple: [Oxford, Maine, adjacentTo, Poland, Maine]
-
A.
Poland, Maine
chosen
Poland, Maine is a small town in southwestern Maine known for its rural character and historic Poland Spring resort and bottled water brand.
-
B.
Sweden, Maine
Sweden, Maine is a small rural town in Oxford County known for its scenic lakeside setting and outdoor recreation opportunities in western Maine.
-
C.
Denmark, Maine
Denmark, Maine is a small rural town in Oxford County known for its lakeside setting in western Maine’s Lakes Region.
-
D.
Norway, Maine
Norway, Maine is a small New England town known for its historic downtown, lakes and outdoor recreation, located in western Maine.
-
E.
Peru, Maine
Peru, Maine is a small rural town in Oxford County known for its scenic western Maine landscape and close-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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6b068a388190962114f3798ef4f9 |
completed | March 9, 2026, 6:39 a.m. |
Created at: March 4, 2026, 7:47 p.m.