Triple
T17733518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 234 |
E442648
|
entity |
| Predicate | terminusB |
P388
|
FINISHED |
| Object | Strong, Maine |
—
|
NE NERFINISHED |
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: Strong, Maine | Statement: [Maine State Route 234, terminusB, Strong, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strong, Maine Context triple: [Maine State Route 234, terminusB, Strong, Maine]
-
A.
Strong, Maine
chosen
Strong, Maine is a small rural town in western Maine known historically for its lumber and toothpick manufacturing industries.
-
B.
Hope, Maine
Hope, Maine is a small rural town in coastal Knox County known for its scenic lakes, rolling hills, and quiet New England character.
-
C.
Freedom, Maine
Freedom, Maine is a small rural town in central Maine known for its scenic countryside and tight-knit community.
-
D.
Gray, Maine
Gray, Maine is a small New England town in southern Maine known for its rural character, proximity to Portland, and the Maine Wildlife Park.
-
E.
Warren, Maine
Warren, Maine is a small town in Knox County known for its rural character and location along the St. George River in midcoast Maine.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e86f188190a5dd7fb32fd04c7b |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 10:08 a.m.