Triple
T23403562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagdo Reservoir |
E559571
|
entity |
| Predicate | formedByStructureType |
P972
|
FINISHED |
| Object | embankment dam |
—
|
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: embankment dam | Statement: [Lagdo Reservoir, formedByStructureType, embankment dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByStructureType Context triple: [Lagdo Reservoir, formedByStructureType, embankment dam]
-
A.
formedBy
chosen
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
B.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
E.
structureTypeBuilt
Indicates the type or kind of structure that was constructed in a building or creation event.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e16f9881908ea4bef465e3af11 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.