Triple
T36062008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union–China border |
E1043112
|
entity |
| Predicate | borderedChineseRegion |
P125855
|
FINISHED |
| Object | Xinjiang |
—
|
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: Xinjiang | Statement: [Soviet Union–China border, borderedChineseRegion, Xinjiang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedChineseRegion Context triple: [Soviet Union–China border, borderedChineseRegion, Xinjiang]
-
A.
autonomousPrefectureInChina
Indicates that one administrative region is an autonomous prefecture located within the territorial jurisdiction of China.
-
B.
borderTypeWithChina
chosen
Indicates the type or nature of the border relationship an entity has with China.
-
C.
specialAdministrativeRegion
Indicates that one region holds a distinct administrative status with a high degree of autonomy under the sovereignty of a larger state.
-
D.
otherProvinceInChina
Indicates that two provinces are distinct from each other while both being located within China.
-
E.
isMainlandTerritoryOf
Indicates that a territory constitutes the primary continental landmass belonging to a particular country or sovereign 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:08 p.m.