Triple
T16045134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 209 |
E389196
|
entity |
| Predicate | terminusCommunity |
P1866
|
FINISHED |
| Object | Phippsburg, 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: Phippsburg, Maine | Statement: [Maine State Route 209, terminusCommunity, Phippsburg, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCommunity Context triple: [Maine State Route 209, terminusCommunity, Phippsburg, Maine]
-
A.
terminusSouthwest
Indicates that one entity serves as the southwestern endpoint or terminal location of another entity (such as a route, line, or path).
-
B.
terminusCity
chosen
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
terminusCoastal
Indicates that the endpoint or terminus of something (e.g., a route, line, or feature) is located on or directly adjacent to a coast.
-
E.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
- F. None of above.
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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.