Triple
T23300923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D & C Builders Ltd v Rees |
E590299
|
entity |
| Predicate | isLeadingCaseOn |
P82359
|
FINISHED |
| Object | economic duress in contract law |
—
|
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: economic duress in contract law | Statement: [D & C Builders Ltd v Rees, isLeadingCaseOn, economic duress in contract law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLeadingCaseOn Context triple: [D & C Builders Ltd v Rees, isLeadingCaseOn, economic duress in contract law]
-
A.
leadingCaseOn
chosen
Indicates that one case serves as the primary or authoritative precedent for another case.
-
B.
isLeadingIn
Indicates that one entity is currently ahead of or outperforming another in a specified context, such as a competition, ranking, or metric.
-
C.
requiresLeadingIn
Indicates that one entity must be introduced, prepared, or preceded by another entity or action before it can appropriately occur or be used.
-
D.
precededAsCapitalBy
Indicates that one capital city previously held the status of capital before being succeeded by another capital city.
-
E.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
- 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.