Triple
T7301982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River Reserve Fleet |
E167878
|
entity |
| Predicate | riverMileMarkerApprox |
P20523
|
FINISHED |
| Object | around 44 miles north of New York City |
—
|
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: around 44 miles north of New York City | Statement: [Hudson River Reserve Fleet, riverMileMarkerApprox, around 44 miles north of New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileMarkerApprox Context triple: [Hudson River Reserve Fleet, riverMileMarkerApprox, around 44 miles north of New York City]
-
A.
approximateMileMarker
chosen
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
B.
riverMileFromMouth
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
C.
riverMileBelowHooverDam
Indicates the position of a location along the river measured in miles downstream from Hoover Dam.
-
D.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
E.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb09164819099c4479d48c1688a |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.