Triple
T16240486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyamiha River |
E394229
|
entity |
| Predicate | currentVisibility |
P74023
|
FINISHED |
| Object | mostly not visible at the surface in central Minsk |
—
|
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: mostly not visible at the surface in central Minsk | Statement: [Nyamiha River, currentVisibility, mostly not visible at the surface in central Minsk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVisibility Context triple: [Nyamiha River, currentVisibility, mostly not visible at the surface in central Minsk]
-
A.
visibilityStatus
chosen
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
D.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
-
E.
visibilityComputation
Indicates the process or relationship by which the visibility of one entity from another is determined or computed.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455e1ce08190b97e2ab3e8c6d535 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.