Triple
T23579352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea |
E582154
|
entity |
| Predicate | historicallyBorderedByCountry |
P47008
|
FINISHED |
| Object | Japan |
—
|
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: Japan | Statement: [Korea, historicallyBorderedByCountry, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyBorderedByCountry Context triple: [Korea, historicallyBorderedByCountry, Japan]
-
A.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
B.
historicBoundaryFor
chosen
Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
E.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1afd8e5ec81909fbdcf68bc14078e |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.