Triple
T7625098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yining |
E172606
|
entity |
| Predicate | borderTradeFunction |
P10963
|
FINISHED |
| Object | gateway between China and Central Asia |
—
|
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: gateway between China and Central Asia | Statement: [Yining, borderTradeFunction, gateway between China and Central Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeFunction Context triple: [Yining, borderTradeFunction, gateway between China and Central Asia]
-
A.
hasBorderCrossingFunction
chosen
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
B.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
C.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.