Triple
T22310311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baishan |
E551492
|
entity |
| Predicate | borderTypeWithNorthKorea |
P147998
|
FINISHED |
| Object | river border |
—
|
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: river border | Statement: [Baishan, borderTypeWithNorthKorea, river border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithNorthKorea Context triple: [Baishan, borderTypeWithNorthKorea, river border]
-
A.
borderTypeWithChina
Indicates the type or nature of the border relationship an entity has with China.
-
B.
borderTypeWithRussia
Indicates the type or nature of a geographic border that an entity shares with Russia.
-
C.
borderTypeWithMongolia
Indicates the specific nature or classification of the border that an entity shares with Mongolia.
-
D.
borderingPoliticalEntityNorth
Indicates that one political entity lies directly to the north of, and shares a border with, another political entity.
-
E.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574d53148190a1ec07f849e1ae9d |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:42 p.m.