Triple
T22348439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khüiten Peak |
E552459
|
entity |
| Predicate | borderZoneRestriction |
P78992
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Khüiten Peak, borderZoneRestriction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderZoneRestriction Context triple: [Khüiten Peak, borderZoneRestriction, yes]
-
A.
borderCrossingsRestrictedSince
Indicates that crossings across a border have been subject to restrictions starting from a specified point in time.
-
B.
movementRestrictions
chosen
Indicates limitations, rules, or prohibitions that constrain how, where, or when an entity is allowed to move.
-
C.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1579a1c308190ae2174f99ae317ab |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.