Triple
T5153026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catskill-Delaware Watershed |
E116241
|
entity |
| Predicate | waterDeliveryMethod |
P29879
|
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-Delaware Watershed, waterDeliveryMethod, gravity-fed aqueduct system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDeliveryMethod Context triple: [Catskill-Delaware Watershed, waterDeliveryMethod, gravity-fed aqueduct system]
-
A.
waterDistributionMethod
chosen
Indicates how water is delivered, supplied, or allocated from a source to its intended recipients or locations.
-
B.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
C.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
D.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
E.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.