Triple
T27524041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–South Korea |
E694786
|
entity |
| Predicate | isMajorTradingPartners |
P9483
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Japan–South Korea, isMajorTradingPartners, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTradingPartners Context triple: [Japan–South Korea, isMajorTradingPartners, true]
-
A.
mainTradingPartnerCountry
Indicates the country that serves as the primary trading partner for a given entity, based on the largest or most significant volume of trade.
-
B.
tradePartnerRegion
Indicates that one entity engages in trade with partners located in a specified geographic region.
-
C.
isLargestTradeBlocBy
Indicates that one trade bloc is the largest according to a specified criterion, such as member count, GDP, or trade volume, relative to other trade blocs.
-
D.
isLinkedEconomicallyTo
chosen
Indicates that two entities are connected through economic relationships such as trade, investment, financial flows, or shared market dependencies.
-
E.
hasMajorCountry
Indicates that an entity includes, is associated with, or is primarily represented by a particular major 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 1:22 p.m.