Triple
T31375145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarine River |
E800273
|
entity |
| Predicate | crossesLanguageBoundary |
P74621
|
FINISHED |
| Object | Röstigraben area |
—
|
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: Röstigraben area | Statement: [Sarine River, crossesLanguageBoundary, Röstigraben area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesLanguageBoundary Context triple: [Sarine River, crossesLanguageBoundary, Röstigraben area]
-
A.
crossBorderLanguage
Indicates a language that is used across national borders, linking communities in more than one country.
-
B.
crossedBoundary
chosen
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
C.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
D.
coexistsWithLanguage
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
-
E.
crossPlatformWith
Indicates that two systems, applications, or components are compatible with or operate across multiple platforms together.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 9:18 p.m.