Triple
T22611076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China–Kazakhstan border |
E566701
|
entity |
| Predicate | delimitationCompleted |
P148927
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [China–Kazakhstan border, delimitationCompleted, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimitationCompleted Context triple: [China–Kazakhstan border, delimitationCompleted, 1998]
-
A.
delimitationBodyEstablishedBy
Indicates that a boundary or delimitation body was formally created or set up by a specified agent or authority.
-
B.
delimitationBody
Indicates the boundary or extent of something, specifying the limits that define where it begins and ends.
-
C.
delimitationMethod
Indicates the method or process used to establish or define the boundaries or limits of something.
-
D.
lastDelimitationOfConstituencies
Indicates the most recent official redrawing or adjustment of electoral constituency boundaries for an entity.
-
E.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
- F. None of above. chosen
Provenance (4 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f167ea291c8190ba73ba678089f75d |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:56 p.m.