Triple
T24837047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts–Rhode Island border |
E621505
|
entity |
| Predicate | hasAdjacentWaterBoundary |
P65207
|
FINISHED |
| Object | state line in Mount Hope Bay |
—
|
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: state line in Mount Hope Bay | Statement: [Massachusetts–Rhode Island border, hasAdjacentWaterBoundary, state line in Mount Hope Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentWaterBoundary Context triple: [Massachusetts–Rhode Island border, hasAdjacentWaterBoundary, state line in Mount Hope Bay]
-
A.
hasWaterBorderWith
chosen
Indicates that two entities share a common boundary that runs along or across a body of water, such as a river, lake, or sea.
-
B.
hasSurroundingWatersStatus
Indicates whether and how an entity is characterized in terms of the presence, type, or condition of waters that surround it.
-
C.
hasHydrologicalBoundary
Indicates that one entity serves as a hydrological boundary or limit for another, typically defining the extent of a water-related area or system.
-
D.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
E.
hasNearbyBoundary
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:18 a.m.