Triple
T28337720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouin Dam |
E717722
|
entity |
| Predicate | hasTypeOfSpillway |
P148103
|
FINISHED |
| Object | gated 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: gated spillway | Statement: [Gouin Dam, hasTypeOfSpillway, gated spillway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSpillway Context triple: [Gouin Dam, hasTypeOfSpillway, gated spillway]
-
A.
typeOfSpillway
chosen
Indicates the specific kind or design category of a spillway associated with a structure or location.
-
B.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
C.
hasAuxiliarySpillway
Indicates that a structure, typically a dam or reservoir, is equipped with an additional spillway used to safely pass excess water beyond the capacity of the main spillway.
-
D.
hasSpillwayGates
Indicates that a structure, typically a dam or spillway, is equipped with one or more controllable gates for regulating water flow.
-
E.
hasNumberOfSpillwayGates
Indicates the specific count of spillway gates associated with a given structure or facility.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:37 a.m.