Triple
T5512736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dora Baltea basin |
E144603
|
entity |
| Predicate | hasTypeOfFlowRegime |
P50263
|
FINISHED |
| Object | Alpine river regime |
—
|
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: Alpine river regime | Statement: [Dora Baltea basin, hasTypeOfFlowRegime, Alpine river regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfFlowRegime Context triple: [Dora Baltea basin, hasTypeOfFlowRegime, Alpine river regime]
-
A.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
B.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
C.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
D.
hasHydrologicalRegime
chosen
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
E.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f581c5081909a8f6d4653edb125 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.