Triple
T27524057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–South Korea |
E694786
|
entity |
| Predicate | hasNameDispute |
P24787
|
FINISHED |
| Object | Sea of Japan naming dispute |
—
|
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: Sea of Japan naming dispute | Statement: [Japan–South Korea, hasNameDispute, Sea of Japan naming dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDispute Context triple: [Japan–South Korea, hasNameDispute, Sea of Japan naming dispute]
-
A.
disputeKnownAs
chosen
Indicates that a particular dispute is also referred to by an alternative name or title.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
D.
contestedOnBrand
Indicates that a dispute, challenge, or competition occurred specifically concerning a particular brand.
-
E.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 1:22 p.m.