Triple
T13482223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrgyzstan–China border |
E318398
|
entity |
| Predicate | disputeHistory |
P3572
|
FINISHED |
| Object | Sino-Soviet border dispute |
—
|
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: Sino-Soviet border dispute | Statement: [Kyrgyzstan–China border, disputeHistory, Sino-Soviet border dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeHistory Context triple: [Kyrgyzstan–China border, disputeHistory, Sino-Soviet border dispute]
-
A.
hasDisputeHistory
chosen
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
B.
disputeNumber
Indicates the identifier or count associated with a specific dispute within a set of disputes.
-
C.
disputeIssue
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
D.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
E.
disputeSettlementNumber
Indicates the identifying number assigned to a specific dispute settlement case or process.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.