Triple
T37031148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Мухавец |
E916497
|
entity |
| Predicate | протекает через |
P27579
|
FINISHED |
| Object | Брест |
—
|
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: Брест | Statement: [Мухавец, протекает через, Брест]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: протекает через Context triple: [Мухавец, протекает через, Брест]
-
A.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
B.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
C.
waterwayThrough
chosen
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
D.
протекаетВдольГраницыС
Indicates that one entity (such as a geographic feature or object) runs or extends along the boundary shared with another entity.
-
E.
passesThroughFacility
Indicates that something (such as a person, object, or shipment) moves through or is routed via a particular facility as part of its path or process.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.