Triple
T19649176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durance valley region |
E471762
|
entity |
| Predicate | hasRiverValleyType |
P136825
|
FINISHED |
| Object | Alpine valley |
—
|
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 valley | Statement: [Durance valley region, hasRiverValleyType, Alpine valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverValleyType Context triple: [Durance valley region, hasRiverValleyType, Alpine valley]
-
A.
hasRiverValley
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
B.
associatedWithRiverValleyCivilization
Indicates that there is a connection or relevance between something and a specific river valley civilization, such as through origin, influence, location, or historical context.
-
C.
locatedInRiverValley
Indicates that something is situated within the geographical area of a river valley.
-
D.
hasRiverValleyAgriculture
Indicates that agriculture is practiced within or along a river valley, utilizing the valley’s river-related resources and conditions.
-
E.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641278e9881909bdf8d440ef6eba4 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.