Triple
T21889302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Brook |
E540493
|
entity |
| Predicate | waterDischarge |
P36349
|
FINISHED |
| Object | Neponset River |
—
|
NE NERFINISHED |
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: Neponset River | Statement: [Mother Brook, waterDischarge, Neponset River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDischarge Context triple: [Mother Brook, waterDischarge, Neponset River]
-
A.
surfaceWaterOutlet
Indicates a relationship where surface water from one location flows out or is discharged through a specific outlet or exit point.
-
B.
currentHydrology
Indicates the present state or characteristics of water flow, distribution, and related hydrological conditions associated with an entity.
-
C.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
D.
regulatesWaterDischargeUnder
Indicates that one entity has authority to control or set rules governing another entity’s release or discharge of water under a specified law, policy, or regulatory framework.
-
E.
outflowWatercourse
chosen
Indicates the watercourse (such as a river, stream, or channel) into which a body of water flows out.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ef2b648190bbd78f6b3958d2ee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:06 p.m.