Triple
T25524001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korkai |
E639729
|
entity |
| Predicate | tradePartnerWith |
P158707
|
FINISHED |
| Object | Southeast Asia |
—
|
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: Southeast Asia | Statement: [Korkai, tradePartnerWith, Southeast Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradePartnerWith Context triple: [Korkai, tradePartnerWith, Southeast Asia]
-
A.
tradePartnerRegion
chosen
Indicates that one entity engages in trade with partners located in a specified geographic region.
-
B.
tradingPartner
Indicates a relationship where two entities engage in the exchange of goods, services, or financial instruments with one another.
-
C.
countryPartner
Indicates a formal partnership relationship between two countries, such as cooperation, alliance, or strategic collaboration.
-
D.
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.
-
E.
tradeBloc
Indicates a formal economic relationship in which entities participate together in a trade bloc, coordinating trade policies and often reducing barriers to commerce among members.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 3:09 p.m.