Triple
T25516732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HM Advocate |
E639526
|
entity |
| Predicate | appearsAsPartyInCaseTitle |
P15954
|
FINISHED |
| Object | Her Majesty's Advocate v [Defender] |
—
|
NE NERFINISHED |
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: Her Majesty's Advocate v [Defender] | Statement: [HM Advocate, appearsAsPartyInCaseTitle, Her Majesty's Advocate v [Defender]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsPartyInCaseTitle Context triple: [HM Advocate, appearsAsPartyInCaseTitle, Her Majesty's Advocate v [Defender]]
-
A.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
courtTitle
Indicates the official judicial position or title held by a person within a court system.
-
C.
isNamedAsPartyIn
Indicates that an entity is explicitly listed or designated as a party in a formal agreement, contract, or legal document.
-
D.
associatedCourtCase
Indicates a relationship where one entity is linked to, or involved in, a particular court case.
-
E.
representedInCourtBy
Indicates that one party serves as the legal representative or attorney for another party in a court proceeding.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:56 p.m.