Triple
T12585667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limmat basin |
E300451
|
entity |
| Predicate | hydrologicalUnitType |
P49162
|
FINISHED |
| Object | catchment area |
—
|
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: catchment area | Statement: [Limmat basin, hydrologicalUnitType, catchment area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydrologicalUnitType Context triple: [Limmat basin, hydrologicalUnitType, catchment area]
-
A.
hydrologicUnitCode
Indicates the standardized hydrologic unit identifier that specifies the drainage or watershed area associated with a given geographic feature or location.
-
B.
watershedType
chosen
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
C.
hydrologicCodeSystem
Indicates the classification or coding system used to identify and organize hydrologic or water-related features.
-
D.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
E.
hydrologyFeature
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:04 p.m.