Triple
T21164072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 286 |
E521511
|
entity |
| Predicate | westernEndpointCity |
P13603
|
FINISHED |
| Object | Saco, 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: Saco, Maine | Statement: [Maine State Route 286, westernEndpointCity, Saco, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernEndpointCity Context triple: [Maine State Route 286, westernEndpointCity, Saco, Maine]
-
A.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
B.
westernTerminusDetail
chosen
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
C.
westernTerminusConnectsTo
Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
-
D.
westernTerminusCrosses
Indicates that the western endpoint of a route, line, or path intersects or passes over another feature or boundary.
-
E.
westernTerminusState
Indicates the state in which something (such as a route, line, or path) has its western endpoint or terminus.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72533fe88819082e14d71c36140be |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.