Triple
T11133193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suella Braverman |
E263339
|
entity |
| Predicate | qualifiedAs |
P24944
|
FINISHED |
| Object | barrister |
—
|
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: barrister | Statement: [Suella Braverman, qualifiedAs, barrister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedAs Context triple: [Suella Braverman, qualifiedAs, barrister]
-
A.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of another entity.
-
B.
hasQualification
chosen
Indicates that an entity possesses a specific qualification, credential, or competency.
-
C.
providedQualificationFor
Indicates that one entity supplied or granted a qualification, credential, or certification that another entity possesses or uses.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8347a248190837e8c26f25f553a |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.