Triple
T14017412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–China relations |
E337237
|
entity |
| Predicate | languageUsedInDiplomacy |
P18759
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Japan–China relations, languageUsedInDiplomacy, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInDiplomacy Context triple: [Japan–China relations, languageUsedInDiplomacy, Japanese]
-
A.
diplomaticLanguage
Indicates the use of polite, tactful, and non-confrontational wording in communication between parties, especially to manage or ease sensitive or potentially conflicting situations.
-
B.
usedDiplomacyWith
Indicates that one entity engaged in diplomatic efforts, negotiations, or formal dialogue with another entity.
-
C.
usedInDiplomacy
chosen
Indicates that something is employed as a tool, method, or resource within diplomatic interactions or negotiations between parties.
-
D.
languageOfTreatyAftermath
Indicates the language used in documents, discourse, or arrangements that arise as a consequence of a treaty’s implementation or aftermath.
-
E.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.