Triple
T2054282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Maine |
E45638
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Orono, Maine |
E65873
|
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: Orono, Maine | Statement: [Eastern Maine, containsTown, Orono, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orono, Maine Context triple: [Eastern Maine, containsTown, Orono, Maine]
-
A.
Orono, Maine
chosen
Orono, Maine is a small town in Penobscot County best known as the home of the University of Maine’s flagship campus.
-
B.
Gardiner, Maine
Gardiner, Maine is a small historic city in central Maine located along the Kennebec River, known for its preserved downtown and 19th-century architecture.
-
C.
Madison, Maine
Madison, Maine is a small town in central Maine known for its rural character, historic mill industry, and location along the Kennebec River.
-
D.
Orono
Orono is a small rural village in Ontario, Canada, known for its historic downtown, agricultural surroundings, and community events.
-
E.
Orono
Orono is a suburban city in Minnesota known for its affluent residential communities and scenic location along the north shore of Lake Minnetonka.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9a8518081909ba95a8ef9321f12 |
completed | March 7, 2026, 5:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a127b0e48190880ee84f45bed359 |
completed | March 23, 2026, 2:10 a.m. |
Created at: March 4, 2026, 7:39 p.m.