Triple
T6257814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mashpee River |
E140215
|
entity |
| Predicate | hasHeadwaters |
P31964
|
FINISHED |
| Object | inland freshwater sources in Mashpee |
—
|
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: inland freshwater sources in Mashpee | Statement: [Mashpee River, hasHeadwaters, inland freshwater sources in Mashpee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadwaters Context triple: [Mashpee River, hasHeadwaters, inland freshwater sources in Mashpee]
-
A.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
B.
formsHeadwatersWith
Indicates that two or more watercourses join or originate together to create the initial source or headwaters of a larger river or stream.
-
C.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
D.
receivesFreshwaterFrom
chosen
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
E.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06366baa481908d59428cceabbe46 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.