Triple
T23300946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D & C Builders Ltd v Rees |
E590299
|
entity |
| Predicate | hasLeadingJudgmentBy |
P94258
|
FINISHED |
| Object | Lord Denning MR |
—
|
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: Lord Denning MR | Statement: [D & C Builders Ltd v Rees, hasLeadingJudgmentBy, Lord Denning MR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadingJudgmentBy Context triple: [D & C Builders Ltd v Rees, hasLeadingJudgmentBy, Lord Denning MR]
-
A.
leadingJudgmentBy
chosen
Indicates a relationship where one judgment or legal decision is treated as the primary or authoritative basis guiding or influencing another judgment.
-
B.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
C.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
-
D.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
E.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.