Triple

T8749317
Position Surface form Disambiguated ID Type / Status
Subject Catskill system reservoirs E207914 entity
Predicate conveysWaterVia P14199 FINISHED
Object gravity-fed aqueduct system 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 aqueduct system | Statement: [Catskill system reservoirs, conveysWaterVia, gravity-fed aqueduct system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conveysWaterVia
Context triple: [Catskill system reservoirs, conveysWaterVia, gravity-fed aqueduct system]
  • A. transportsWaterTo chosen
    Indicates that one entity carries or conveys water from its location or source to another entity or destination.
  • B. transportsWaterFrom
    Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
  • C. usedWaterway
    Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
  • D. waterwayThrough
    Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
  • E. waterwayServed
    Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
  • 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_69ca835bb2bc819084bb5906cb6ef7f8 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5da4214881908b6917f847c43cb5 completed March 31, 2026, 11:49 p.m.
PD Predicate disambiguation batch_69cc5c160dac8190b4aeb4bf0529de52 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:39 p.m.