Triple
T27909529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klosters |
E705882
|
entity |
| Predicate | cantonCapitalDistance |
P122332
|
FINISHED |
| Object | near Chur |
—
|
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: near Chur | Statement: [Klosters, cantonCapitalDistance, near Chur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cantonCapitalDistance Context triple: [Klosters, cantonCapitalDistance, near Chur]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
C.
distanceToProvinceCapital_km
Indicates the distance, measured in kilometers, between a given location and the capital city of its province.
-
D.
prefecturalCapitalDistanceRelation
Indicates a spatial relationship specifying the distance between an entity and the capital city of its prefecture.
-
E.
distanceFromRegionalCapital
chosen
Indicates the measured spatial distance between a given place and its corresponding regional capital.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:48 p.m.