Triple
T26655589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monponsett Pond |
E666491
|
entity |
| Predicate | waterUseRegulatedBy |
P44590
|
FINISHED |
| Object | state permits |
—
|
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 permits | Statement: [Monponsett Pond, waterUseRegulatedBy, state permits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterUseRegulatedBy Context triple: [Monponsett Pond, waterUseRegulatedBy, state permits]
-
A.
waterUseRestrictions
chosen
Indicates that there are rules or limitations imposed on how much, when, or for what purposes water may be used.
-
B.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
C.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
D.
waterAllocatedTo
Indicates that a specified amount or portion of water has been designated or assigned for use by a particular entity, location, or purpose.
-
E.
waterManagementAuthority
Indicates that an entity has official responsibility for overseeing, regulating, or managing water resources, services, or infrastructure for a given area or system.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 2:34 a.m.