Triple
T36751348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lang Son |
E907922
|
entity |
| Predicate | borderWithChineseRegion |
P190994
|
FINISHED |
| Object | Guangxi Zhuang Autonomous Region |
—
|
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: Guangxi Zhuang Autonomous Region | Statement: [Lang Son, borderWithChineseRegion, Guangxi Zhuang Autonomous Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderWithChineseRegion Context triple: [Lang Son, borderWithChineseRegion, Guangxi Zhuang Autonomous Region]
-
A.
borderTypeWithChina
Indicates the type or nature of the border relationship an entity has with China.
-
B.
borderTypeWithMongolia
Indicates the specific nature or classification of the border that an entity shares with Mongolia.
-
C.
borderWithTerritory
chosen
Indicates that one territory shares a common boundary or border with another territory.
-
D.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:12 p.m.