Triple
T12807069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blowering Dam |
E306171
|
entity |
| Predicate | typeOfEmbankment |
P103573
|
FINISHED |
| Object | rockfill with clay core |
—
|
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: rockfill with clay core | Statement: [Blowering Dam, typeOfEmbankment, rockfill with clay core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEmbankment Context triple: [Blowering Dam, typeOfEmbankment, rockfill with clay core]
-
A.
hasEmbankmentMaterial
chosen
Indicates that an embankment is composed of, or constructed using, a specified material.
-
B.
hasEmbankment
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
C.
typeOfDam
Indicates the specific kind or classification of a dam associated with an entity.
-
D.
typeOfWeir
Indicates that one entity is a specific kind or classification of weir in relation to another entity.
-
E.
typeOfDamProject
Indicates that a given project is classified as a dam-related project (i.e., it is a project whose type is a dam project).
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.