Triple
T25851408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reedham Ferry |
E651219
|
entity |
| Predicate | roadLinkFor |
P131761
|
FINISHED |
| Object | local road network near Reedham |
—
|
LITERAL FINISHED |
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: local road network near Reedham | Statement: [Reedham Ferry, roadLinkFor, local road network near Reedham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadLinkFor Context triple: [Reedham Ferry, roadLinkFor, local road network near Reedham]
-
A.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
B.
roadAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
-
C.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
D.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
E.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023b96208190925872085ada10e3 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:58 a.m.