Triple
T36062018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union–China border |
E1043112
|
entity |
| Predicate | laterDemarcationAgreement |
P110561
|
FINISHED |
| Object | 1991 Sino-Soviet border agreement |
—
|
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: 1991 Sino-Soviet border agreement | Statement: [Soviet Union–China border, laterDemarcationAgreement, 1991 Sino-Soviet border agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDemarcationAgreement Context triple: [Soviet Union–China border, laterDemarcationAgreement, 1991 Sino-Soviet border agreement]
-
A.
finalDemarcationInstrument
Indicates the formal document or instrument that definitively establishes and records the final boundary or demarcation between entities.
-
B.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
C.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
D.
hasDemarcationAuthority
Indicates that an entity possesses the formal power or right to define, set, or modify boundaries or divisions between areas, responsibilities, or categories.
-
E.
subsequentAgreement
chosen
Indicates that a later agreement or understanding was reached that follows and potentially modifies or supplements an earlier one.
- 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_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.