Triple
T15757602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innerste |
E382006
|
entity |
| Predicate | Innerste DamLocatedIn |
P31704
|
FINISHED |
| Object | Upper Innerste valley near Lautenthal |
—
|
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: Upper Innerste valley near Lautenthal | Statement: [Innerste, Innerste DamLocatedIn, Upper Innerste valley near Lautenthal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Innerste DamLocatedIn Context triple: [Innerste, Innerste DamLocatedIn, Upper Innerste valley near Lautenthal]
-
A.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
B.
damLocation
chosen
Indicates the geographic place where a dam is situated or constructed.
-
C.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
D.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
E.
locatedInland
Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.