Triple
T21493272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanaye lock complex |
E530288
|
entity |
| Predicate | waterLevelDifference |
P144588
|
FINISHED |
| Object | approximately 13.9 metres |
—
|
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: approximately 13.9 metres | Statement: [Lanaye lock complex, waterLevelDifference, approximately 13.9 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterLevelDifference Context triple: [Lanaye lock complex, waterLevelDifference, approximately 13.9 metres]
-
A.
waterLevelTrend
Indicates the direction and rate at which a body of water’s level is changing over time (e.g., rising, falling, or stable).
-
B.
waterLevelTransition
Indicates a change in water level from one state or value to another over time.
-
C.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
D.
reservoirElevation
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
E.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
- F. None of above. chosen
Provenance (4 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea54fb608190a147cd8aa6d6d04b |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:23 p.m.