Triple
T25495604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Townsend–Coupeville ferry |
E638953
|
entity |
| Predicate | connectsRoadNetwork |
P170603
|
FINISHED |
| Object | State Route 20 |
—
|
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: State Route 20 | Statement: [Port Townsend–Coupeville ferry, connectsRoadNetwork, State Route 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRoadNetwork Context triple: [Port Townsend–Coupeville ferry, connectsRoadNetwork, State Route 20]
-
A.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
B.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
C.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
D.
roadConnectionRegion
Indicates that a road provides a direct transportation connection between two regions.
-
E.
roadNetworkServedBy
Indicates that a particular road network is provided, maintained, or operated by a specified service, organization, or infrastructure system.
- F. None of above. chosen
Provenance (4 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 21, 2026, 2:40 p.m.