Triple
T37260342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African embassy in Buenos Aires |
E924239
|
entity |
| Predicate | locatedOnContinentOfHostCountry |
P203380
|
FINISHED |
| Object | South America |
E1813
|
NE 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: South America | Statement: [South African embassy in Buenos Aires, locatedOnContinentOfHostCountry, South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnContinentOfHostCountry Context triple: [South African embassy in Buenos Aires, locatedOnContinentOfHostCountry, South America]
-
A.
locatedInContinentOfHostCountry
chosen
Indicates that something is situated within the continent on which its host country is located.
-
B.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
-
C.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
D.
locatedInCountryOfOperatedVenue
Indicates that an entity is situated within the country where a related venue operates.
-
E.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
- F. None of above.
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40637f78c48190979824f9ff6a9fdb |
completed | June 27, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.