Triple
T37091802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebensfeld |
E918441
|
entity |
| Predicate | isPartOfRiverValley |
P27424
|
FINISHED |
| Object | Main 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: Main valley | Statement: [Ebensfeld, isPartOfRiverValley, Main valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRiverValley Context triple: [Ebensfeld, isPartOfRiverValley, Main valley]
-
A.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
B.
hasRiverValley
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
C.
locatedInRiverValley
chosen
Indicates that something is situated within the geographical area of a river valley.
-
D.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
E.
isRegionalRiver
Indicates that a river is classified as a regional river, typically limited in geographic extent and significance to a specific region rather than being a major or national waterway.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:14 p.m.