Triple
T32604967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earls Cove–Saltery Bay ferry route |
E833480
|
entity |
| Predicate | roadConnectionAt |
P41155
|
FINISHED |
| Object | Highway 101 at Earls Cove |
—
|
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: Highway 101 at Earls Cove | Statement: [Earls Cove–Saltery Bay ferry route, roadConnectionAt, Highway 101 at Earls Cove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadConnectionAt Context triple: [Earls Cove–Saltery Bay ferry route, roadConnectionAt, Highway 101 at Earls Cove]
-
A.
roadConnectionRegion
Indicates that a road provides a direct transportation connection between two regions.
-
B.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
C.
roadJunctionRelation
chosen
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
D.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
-
E.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:05 a.m.