Triple
T5618922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrivener Dam |
E147549
|
entity |
| Predicate | gatedSpillway |
P57427
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Scrivener Dam, gatedSpillway, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatedSpillway Context triple: [Scrivener Dam, gatedSpillway, yes]
-
A.
hasSpillwayGates
chosen
Indicates that a structure, typically a dam or spillway, is equipped with one or more controllable gates for regulating water flow.
-
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.
hasLockAndDamSystem
Indicates that one entity possesses or is equipped with a system of locks and dams used to control water levels and facilitate navigation.
-
E.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dd5d0081909d18d16596fac507 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.