Triple
T24246973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy–Menands Bridge area near Troy, New York |
E603402
|
entity |
| Predicate | roadConnected |
P11435
|
FINISHED |
| Object | U.S. Route 4 |
—
|
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: U.S. Route 4 | Statement: [Troy–Menands Bridge area near Troy, New York, roadConnected, U.S. Route 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadConnected Context triple: [Troy–Menands Bridge area near Troy, New York, roadConnected, U.S. Route 4]
-
A.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
-
B.
roadConnectionRegion
Indicates that a road provides a direct transportation connection between two regions.
-
C.
linkedByRoadTo
chosen
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b85349481909c21dacd48df7b8e |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.