Triple
T5370669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croton River below New Croton Dam |
E108840
|
entity |
| Predicate | flowRegulation |
P20749
|
FINISHED |
| Object | dam-controlled |
—
|
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: dam-controlled | Statement: [Croton River below New Croton Dam, flowRegulation, dam-controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowRegulation Context triple: [Croton River below New Croton Dam, flowRegulation, dam-controlled]
-
A.
riverControl
Indicates a relationship where one entity manages, regulates, or exerts authority over the flow, usage, or conditions of a river.
-
B.
regulatesOutflowOf
chosen
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
C.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
D.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
E.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.