Triple
T21733432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberhalbstein |
E536462
|
entity |
| Predicate | hasValleyOrientation |
P68761
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Oberhalbstein, hasValleyOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValleyOrientation Context triple: [Oberhalbstein, hasValleyOrientation, north–south]
-
A.
valleyOrientation
chosen
Indicates the directional alignment or bearing along which a valley extends across the landscape.
-
B.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
C.
hasSummitRidgeOrientation
Indicates the directional alignment or orientation of a summit ridge relative to cardinal or geographic directions.
-
D.
isInValley
Indicates that an entity is located within or occupies the area of a valley.
-
E.
isOppositeSideOfValleyFrom
Indicates that two entities are located on facing sides of the same valley, with the valley lying between them.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd09852c8190b3486c09f22ef92b |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.