Triple
T4880938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hingham Bay |
E109323
|
entity |
| Predicate | isPartOfNavigationRoute |
P6309
|
FINISHED |
| Object | Boston Harbor approaches |
—
|
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: Boston Harbor approaches | Statement: [Hingham Bay, isPartOfNavigationRoute, Boston Harbor approaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNavigationRoute Context triple: [Hingham Bay, isPartOfNavigationRoute, Boston Harbor approaches]
-
A.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
B.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
C.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
E.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dc071d4819083ea9fd0c73c5f49 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.