Triple
T27865301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mischabel ridge traverse |
E704342
|
entity |
| Predicate | dominatingTown |
P92693
|
FINISHED |
| Object | Saas-Fee |
—
|
NE NERFINISHED |
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: Saas-Fee | Statement: [Mischabel ridge traverse, dominatingTown, Saas-Fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominatingTown Context triple: [Mischabel ridge traverse, dominatingTown, Saas-Fee]
-
A.
dominatingFeature
Indicates that one feature stands out as the most prominent or influential characteristic in relation to others.
-
B.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
C.
primaryTown
chosen
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
D.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
-
E.
dominanceRegion
Indicates that one entity exerts primary control, influence, or priority over a defined area, range, or scope relative to others.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 6:20 p.m.