Triple
T33465147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley Drummle |
E857023
|
entity |
| Predicate | legalClientOf |
P8814
|
FINISHED |
| Object | Mr. Jaggers |
—
|
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: Mr. Jaggers | Statement: [Bentley Drummle, legalClientOf, Mr. Jaggers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalClientOf Context triple: [Bentley Drummle, legalClientOf, Mr. Jaggers]
-
A.
lawPartnerOf
Indicates a professional relationship in which two individuals are partners in the same law firm or legal practice.
-
B.
legalEntityOf
Indicates that one entity is the legally recognized organization or body to which another entity belongs or with which it is formally associated.
-
C.
legalRepresentation
chosen
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
D.
organizationRepresentedTo
Indicates that one entity formally acts on behalf of or serves as the representative of an organization in a given context or interaction.
-
E.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:37 a.m.