Triple
T19456973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow–Brest route |
E486758
|
entity |
| Predicate | importanceForBelarus |
P1887
|
FINISHED |
| Object | main axis linking Belarus with Russia |
—
|
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: main axis linking Belarus with Russia | Statement: [Moscow–Brest route, importanceForBelarus, main axis linking Belarus with Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceForBelarus Context triple: [Moscow–Brest route, importanceForBelarus, main axis linking Belarus with Russia]
-
A.
statusInBelarus
Indicates the legal, social, or official standing or condition that an entity has within the context of Belarus.
-
B.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
C.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
nameInBelarusian
Indicates that an entity is known or referred to by a specific name in the Belarusian language.
-
E.
relativeImportanceInCountry
Indicates the comparative significance or priority of something within the context of a specific country.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c4088881908f23f25a82a513f6 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.