Triple
T3560991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Cascade |
E75336
|
entity |
| Predicate | waterSupplySystem |
P29879
|
FINISHED |
| Object | gravity-fed system without pumps |
—
|
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: gravity-fed system without pumps | Statement: [Grand Cascade, waterSupplySystem, gravity-fed system without pumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSupplySystem Context triple: [Grand Cascade, waterSupplySystem, gravity-fed system without pumps]
-
A.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
B.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
waterDistributionMethod
chosen
Indicates how water is delivered, supplied, or allocated from a source to its intended recipients or locations.
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08ac1b0819082021ecdd0061dc3 |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.