Triple
T10067244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerset County, Maine |
E213131
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Cornville, Maine |
E169264
|
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: Cornville, Maine | Statement: [Somerset County, Maine, containsTown, Cornville, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cornville, Maine Context triple: [Somerset County, Maine, containsTown, Cornville, Maine]
-
A.
Cornville, Maine
chosen
Cornville, Maine is a small rural town located in central Maine known for its agricultural character and quiet, scenic setting.
-
B.
Montville, Maine
Montville, Maine is a small rural town in central Maine known for its forests, farms, and quiet, scenic countryside.
-
C.
Woodville, Maine
Woodville, Maine is a small rural town located in Penobscot County in the central part of the state.
-
D.
Burnham, Maine
Burnham, Maine is a small rural town in central Maine known for its lakes, forests, and quiet residential character.
-
E.
Newburgh, Maine
Newburgh, Maine is a small rural town in central Maine known for its agricultural character and quiet residential 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff63a4c8190bb08a0428aafa189 |
completed | April 2, 2026, 2:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74602a7ec8190980e5e6a80aa1235 |
completed | May 3, 2026, 12:56 p.m. |
Created at: March 30, 2026, 8:58 p.m.