Triple
T14331908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberhausen lock |
E355367
|
entity |
| Predicate | isEngineeringStructureType |
P64156
|
FINISHED |
| Object | hydraulic engineering structure |
—
|
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: hydraulic engineering structure | Statement: [Oberhausen lock, isEngineeringStructureType, hydraulic engineering structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEngineeringStructureType Context triple: [Oberhausen lock, isEngineeringStructureType, hydraulic engineering structure]
-
A.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
B.
designedStructureType
chosen
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
D.
typeOfEngineering
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
E.
hasStructuralEngineer
Indicates that an entity is associated with or employs a structural engineer responsible for its structural design, analysis, or integrity.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1fb87c81908412c2953243c8e3 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.