Triple
T37260222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa–South Korea relations |
E924237
|
entity |
| Predicate | SouthKoreanEmbassyLocation |
P187676
|
FINISHED |
| Object | Pretoria |
—
|
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: Pretoria | Statement: [South Africa–South Korea relations, SouthKoreanEmbassyLocation, Pretoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SouthKoreanEmbassyLocation Context triple: [South Africa–South Korea relations, SouthKoreanEmbassyLocation, Pretoria]
-
A.
NorthKoreaDiplomaticRepresentation
Indicates the existence, level, or nature of diplomatic representation or relations involving North Korea and another state or international entity.
-
B.
USEmbassyLocation
Indicates that a specified location is the site where the United States embassy for a particular country is situated.
-
C.
SouthAfricanEmbassyLocation
Indicates the location where the South African embassy is situated or hosted.
-
D.
chineseEmbassyLocation
Indicates the location where a Chinese embassy is situated or hosted.
-
E.
confederationOfSouthKorea
Indicates a political or organizational confederation that includes or is formed by South Korea.
- 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_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.