Triple
T35203447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uiju County |
E1016470
|
entity |
| Predicate | hasBorderingForeignAdministrativeUnit |
P43880
|
FINISHED |
| Object | Dandong |
—
|
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: Dandong | Statement: [Uiju County, hasBorderingForeignAdministrativeUnit, Dandong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderingForeignAdministrativeUnit Context triple: [Uiju County, hasBorderingForeignAdministrativeUnit, Dandong]
-
A.
hasBorderWithNonSovereignEntity
chosen
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
B.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
C.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:02 p.m.