Triple
T3942750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanhaiguan Pass |
E92072
|
entity |
| Predicate | regionBorder |
P10768
|
FINISHED |
| Object | historical border between China proper and Manchuria |
—
|
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: historical border between China proper and Manchuria | Statement: [Shanhaiguan Pass, regionBorder, historical border between China proper and Manchuria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionBorder Context triple: [Shanhaiguan Pass, regionBorder, historical border between China proper and Manchuria]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.