Triple
T5210155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Counsel |
E117610
|
entity |
| Predicate | typeOfAdvocate |
P5610
|
FINISHED |
| Object | senior advocate |
—
|
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: senior advocate | Statement: [Queen's Counsel, typeOfAdvocate, senior advocate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAdvocate Context triple: [Queen's Counsel, typeOfAdvocate, senior advocate]
-
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.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
C.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
D.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
E.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a703e388190845dedd17252ddde |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.