Triple
T32288277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transbaikal Military District |
E824893
|
entity |
| Predicate | borderRegionNear |
P12818
|
FINISHED |
| Object | Mongolia |
—
|
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: Mongolia | Statement: [Transbaikal Military District, borderRegionNear, Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegionNear Context triple: [Transbaikal Military District, borderRegionNear, Mongolia]
-
A.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
B.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
C.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
-
D.
borderTerminusNearby
Indicates that the endpoint of a border or boundary lies close to a specified reference location or feature.
-
E.
borderRegionPresence
Indicates the presence or occurrence of something within or along a border region between areas or territories.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 1, 2026, 12:44 a.m.