Triple
T5940277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCOP |
E132148
|
entity |
| Predicate | delegationRepresents |
P18461
|
FINISHED |
| Object | each province 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: each province of South Africa | Statement: [NCOP, delegationRepresents, each province of South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delegationRepresents Context triple: [NCOP, delegationRepresents, each province of South Africa]
-
A.
delegates
Indicates that one entity assigns or entrusts a task, responsibility, or authority to another entity to act on its behalf.
-
B.
memberRepresents
chosen
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity within a group, organization, or body.
-
C.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
D.
representativeDetermined
Indicates that an official representative has been identified and designated for a particular entity or context.
-
E.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.