Triple
T37260244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa–South Korea relations |
E924237
|
entity |
| Predicate | SouthKoreaIsMemberOf |
P188935
|
FINISHED |
| Object | G20 |
—
|
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: G20 | Statement: [South Africa–South Korea relations, SouthKoreaIsMemberOf, G20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SouthKoreaIsMemberOf Context triple: [South Africa–South Korea relations, SouthKoreaIsMemberOf, G20]
-
A.
SouthKoreaIs
Indicates that something has the status, identity, or characteristic of being South Korea.
-
B.
confederationOfSouthKorea
Indicates a political or organizational confederation that includes or is formed by South Korea.
-
C.
NorthKoreaDiplomaticRepresentation
Indicates the existence, level, or nature of diplomatic representation or relations involving North Korea and another state or international entity.
-
D.
resultForSouthKorea
Indicates that an outcome, result, or performance metric is associated with or recorded for South Korea.
-
E.
NorthKoreaDependence
Indicates a relationship where one party relies on or is significantly influenced by North Korea for support, resources, or strategic backing.
- F. None of above. chosen
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:15 p.m.