Triple
T28014472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK High Commissioner to South Africa |
E707507
|
entity |
| Predicate | postHoldersAreUsually |
P9583
|
FINISHED |
| Object | career diplomats |
—
|
LITERAL 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: career diplomats | Statement: [UK High Commissioner to South Africa, postHoldersAreUsually, career diplomats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postHoldersAreUsually Context triple: [UK High Commissioner to South Africa, postHoldersAreUsually, career diplomats]
-
A.
primaryHoldersInclude
Indicates that the specified set of primary holders contains, among its members, the referenced entity or entities.
-
B.
officeHoldersAreUsually
chosen
Indicates that individuals holding a particular office or position are typically or generally characterized by a specified property or role.
-
C.
commonHolder
Indicates that two or more entities share the same holder, owner, or controlling party.
-
D.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
E.
eligibleHolders
Indicates which entities are permitted or qualified to hold or possess a given item, right, or role.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:05 p.m.