Triple
T23554703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinwald dialect |
E578150
|
entity |
| Predicate | isLocalVarietyOf |
P95273
|
FINISHED |
| Object | Sutsilvan Romansh |
—
|
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: Sutsilvan Romansh | Statement: [Rheinwald dialect, isLocalVarietyOf, Sutsilvan Romansh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalVarietyOf Context triple: [Rheinwald dialect, isLocalVarietyOf, Sutsilvan Romansh]
-
A.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
B.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or entity.
-
C.
isRecognizedAsVarietyOf
chosen
Indicates that one entity is acknowledged or classified as a specific variety or subtype of another entity.
-
D.
hasNeighboringVariety
Indicates that one variety is geographically or spatially adjacent to another variety.
-
E.
closelyRelatedVariety
Indicates that one variety is very similar to another, differing only in minor or closely related characteristics.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed253788190ba75109af0e91b37 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.