Triple
T20615829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal du Centre |
E506561
|
entity |
| Predicate | elevationChangeManagedBy |
P140793
|
FINISHED |
| Object | boat lifts |
—
|
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: boat lifts | Statement: [Canal du Centre, elevationChangeManagedBy, boat lifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationChangeManagedBy Context triple: [Canal du Centre, elevationChangeManagedBy, boat lifts]
-
A.
elevationChangeRole
Indicates the specific role an entity plays in causing, measuring, or being affected by a change in elevation between locations or points.
-
B.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
-
C.
elevationThreshold
Indicates a specified elevation level at which a condition, effect, or change in state becomes applicable or is triggered.
-
D.
elevationHolder
Indicates that one entity serves as the reference or container for the elevation (height above a baseline) associated with another entity.
-
E.
environmentManagedBy
Indicates that the control, maintenance, or oversight of an environment is carried out by a specified managing entity.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadbb3ac81908145f57fd6a94256 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.