Triple
T36990502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridgewood Reservoir |
E915082
|
entity |
| Predicate | ceasedWaterSupplyRole |
P186869
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Ridgewood Reservoir, ceasedWaterSupplyRole, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedWaterSupplyRole Context triple: [Ridgewood Reservoir, ceasedWaterSupplyRole, 20th century]
-
A.
waterInfrastructureRole
Indicates the functional role or involvement an entity has in the provision, management, or operation of water infrastructure systems.
-
B.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
hasWaterServiceFrom
Indicates that one entity receives its water supply or water-related services from another entity.
-
D.
hasObligationToDeliverWaterTo
Indicates that one party is bound by a duty or agreement to provide or supply water to another party.
-
E.
drainageRole
Indicates the functional role an entity plays in a drainage system, such as directing, collecting, or removing water or other fluids.
- F. None of above. chosen
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.