Triple
T9548476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonds–Kingston |
E230356
|
entity |
| Predicate | connectsToRoadNetworkAtEdmonds |
P12245
|
FINISHED |
| Object | State Route 104 |
—
|
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 104 | Statement: [Edmonds–Kingston, connectsToRoadNetworkAtEdmonds, State Route 104]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToRoadNetworkAtEdmonds Context triple: [Edmonds–Kingston, connectsToRoadNetworkAtEdmonds, State Route 104]
-
A.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
C.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
- 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99059138819088ae54b26df979cf |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.