Triple
T247714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrice Motsepe |
E5074
|
entity |
| Predicate | legalQualification |
P5610
|
FINISHED |
| Object | attorney |
—
|
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: attorney | Statement: [Patrice Motsepe, legalQualification, attorney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalQualification Context triple: [Patrice Motsepe, legalQualification, attorney]
-
A.
legalProfessionRole
chosen
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
B.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
D.
practicedLawIn
Indicates that a person engaged in the professional practice of law within a specified jurisdiction or location.
-
E.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.