Triple
T13693706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barker Slough Pumping Plant |
E328331
|
entity |
| Predicate | waterConveyanceType |
P14199
|
FINISHED |
| Object | aqueduct supply |
—
|
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: aqueduct supply | Statement: [Barker Slough Pumping Plant, waterConveyanceType, aqueduct supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterConveyanceType Context triple: [Barker Slough Pumping Plant, waterConveyanceType, aqueduct supply]
-
A.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
B.
transportsWaterTo
chosen
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
C.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
D.
waterInfrastructure
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
E.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.