Triple
T27524064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–South Korea |
E694786
|
entity |
| Predicate | hasDisputeResolutionChannel |
P6659
|
FINISHED |
| Object | bilateral talks |
—
|
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: bilateral talks | Statement: [Japan–South Korea, hasDisputeResolutionChannel, bilateral talks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputeResolutionChannel Context triple: [Japan–South Korea, hasDisputeResolutionChannel, bilateral talks]
-
A.
hasDisputeResolutionBody
Indicates that there exists a designated body or authority responsible for resolving disputes related to the associated entity or relationship.
-
B.
hasDisputeRegime
Indicates that there exists a specific dispute-handling framework, system, or set of rules governing how disputes related to the subject are managed or resolved.
-
C.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
D.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
-
E.
methodOfDisputeResolution
chosen
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 1:22 p.m.