Triple
T31605576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sense District |
E806474
|
entity |
| Predicate | borderLanguageBoundary |
P77518
|
FINISHED |
| Object | Röstigraben |
—
|
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: Röstigraben | Statement: [Sense District, borderLanguageBoundary, Röstigraben]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLanguageBoundary Context triple: [Sense District, borderLanguageBoundary, Röstigraben]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
languageAlongBorder
chosen
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
D.
borderDialectOf
Indicates a dialect that is spoken in a border area and is linguistically associated with or derived from a particular neighboring language or dialect.
-
E.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: April 30, 2026, 10:34 p.m.