Triple
T31428374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube in Lower Austria |
E801727
|
entity |
| Predicate | formsValleyType |
P22913
|
FINISHED |
| Object | river 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: river valley | Statement: [Danube in Lower Austria, formsValleyType, river valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsValleyType Context triple: [Danube in Lower Austria, formsValleyType, river valley]
-
A.
valleyType
chosen
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
B.
formsValleySystemWith
Indicates that one valley is geographically connected with another to collectively form a larger, integrated valley system.
-
C.
valleyFormed
Indicates that a valley has come into existence or been shaped, typically through geological or erosional processes.
-
D.
valleyForms
Indicates that a valley comes into existence or is shaped as a result of a specified geological or environmental process or agent.
-
E.
valleySystem
Indicates a relationship where a valley is part of, associated with, or characterized by a particular valley system or network of valleys.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 30, 2026, 8:55 p.m.