Triple
T8325974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. G. Strijdom Tunnel |
E194954
|
entity |
| Predicate | hasAssociatedPersonRole |
P27764
|
FINISHED |
| Object | Prime Minister of South Africa |
—
|
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: Prime Minister of South Africa | Statement: [J. G. Strijdom Tunnel, hasAssociatedPersonRole, Prime Minister of South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedPersonRole Context triple: [J. G. Strijdom Tunnel, hasAssociatedPersonRole, Prime Minister of South Africa]
-
A.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
B.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
C.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
D.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7fba688190b696593dfb2cde5d |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.