Triple
T23725752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China–North Korea border system |
E586268
|
entity |
| Predicate | hasBorderSegmentType |
P1972
|
FINISHED |
| Object | land 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: land border | Statement: [China–North Korea border system, hasBorderSegmentType, land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderSegmentType Context triple: [China–North Korea border system, hasBorderSegmentType, land border]
-
A.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
B.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
C.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
D.
hasBorderMarkerType
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
E.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b914adc08190b339c7f83f1536d7 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:08 p.m.