Triple
T34200036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Service Medal (South Africa) |
E877350
|
entity |
| Predicate | locationOfAwardingAuthority |
P19414
|
FINISHED |
| Object | Pretoria |
E5262
|
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: Pretoria | Statement: [General Service Medal (South Africa), locationOfAwardingAuthority, Pretoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfAwardingAuthority Context triple: [General Service Medal (South Africa), locationOfAwardingAuthority, Pretoria]
-
A.
locationOfAwardingBody
chosen
Indicates the place or venue where the awarding body confers or grants an award.
-
B.
registrationAuthorityLocatedIn
Indicates that the authority responsible for registration is situated within a specified geographic or jurisdictional location.
-
C.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
-
D.
hasAwardingBodyHeadquarters
Indicates that an awarding body has its main headquarters located at a specific place.
-
E.
locationOfAwardedWork
Indicates the place where the work for which an award was given was created, performed, or took place.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc89b79c8190b52e36025a16441e |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.