Triple
T20060204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmore Falls |
E499448
|
entity |
| Predicate | waterFlowControl |
P130170
|
FINISHED |
| Object | opened and closed at scheduled times |
—
|
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: opened and closed at scheduled times | Statement: [Marmore Falls, waterFlowControl, opened and closed at scheduled times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowControl Context triple: [Marmore Falls, waterFlowControl, opened and closed at scheduled times]
-
A.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
B.
controlsWaterLevelOf
chosen
Indicates that one entity has the ability or authority to regulate or adjust the water level of another entity or system.
-
C.
waterFlowDependsOn
Indicates that the occurrence, direction, or amount of water flow is determined or constrained by another specified factor or condition.
-
D.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
E.
waterInput
Indicates that an entity receives or is supplied with water from another source 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.