Triple
T12421964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsborough River |
E296795
|
entity |
| Predicate | isNavigableInLowerReaches |
P72144
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hillsborough River, isNavigableInLowerReaches, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNavigableInLowerReaches Context triple: [Hillsborough River, isNavigableInLowerReaches, true]
-
A.
navigableInLowerCourse
chosen
Indicates that a watercourse is suitable for navigation specifically in its lower (downstream) section.
-
B.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
C.
navigableTo
Indicates that one entity can be reached or traversed to from another entity, typically following valid paths or connections within a system or environment.
-
D.
isNavigableNear
Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
-
E.
navigableFor
Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.