Triple
T16402653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeks Footbridge |
E398337
|
entity |
| Predicate | hasRiverMile |
P55788
|
FINISHED |
| Object | approximately 1.5 miles upstream from Boston Harbor |
—
|
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: approximately 1.5 miles upstream from Boston Harbor | Statement: [Weeks Footbridge, hasRiverMile, approximately 1.5 miles upstream from Boston Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverMile Context triple: [Weeks Footbridge, hasRiverMile, approximately 1.5 miles upstream from Boston Harbor]
-
A.
riverMilepost
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
B.
riverMileFromMouth
chosen
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
C.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
D.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
E.
hasApproxLengthAlongRiver
Indicates that an entity has an approximate measured length that follows the course of a river rather than a straight-line distance.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d0652081908f42f78b156f3ae7 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.