Triple
T4464969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangwon Province, North Korea |
E98353
|
entity |
| Predicate | borderTypeWithSouthKorea |
P3948
|
FINISHED |
| Object | militarized 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: militarized border | Statement: [Gangwon Province, North Korea, borderTypeWithSouthKorea, militarized border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithSouthKorea Context triple: [Gangwon Province, North Korea, borderTypeWithSouthKorea, militarized border]
-
A.
borderTypeWithYemen
Indicates the type or nature of the border that exists between a given entity and Yemen.
-
B.
borderRegime
chosen
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
demilitarizedBorderWith
Indicates that a border between two entities exists where military forces, installations, and activities are restricted or prohibited by agreement.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35697937c8190b91f72d9e4f945f6 |
completed | March 13, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.