Triple
T30769704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenkang Wa |
E783482
|
entity |
| Predicate | borderlandCommunity |
P55550
|
FINISHED |
| Object | China–Myanmar frontier region |
—
|
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: China–Myanmar frontier region | Statement: [Zhenkang Wa, borderlandCommunity, China–Myanmar frontier region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderlandCommunity Context triple: [Zhenkang Wa, borderlandCommunity, China–Myanmar frontier region]
-
A.
crossBorderCommunity
chosen
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
-
B.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 29, 2026, 8:40 p.m.