Triple
T588514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Croton Dam |
E17213
|
entity |
| Predicate | spillwayType |
P15114
|
FINISHED |
| Object | overflow spillway |
—
|
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: overflow spillway | Statement: [New Croton Dam, spillwayType, overflow spillway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spillwayType Context triple: [New Croton Dam, spillwayType, overflow spillway]
-
A.
hasSpillway
chosen
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
B.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
flowsIntoBodyOfWaterType
Indicates that one body of water moves or drains into another body of water of a specified type (e.g., river, lake, ocean).
-
E.
drainagePattern
Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9d1e68819096a9b5e7b2e83d6e |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.