Triple
T11826014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specific Relief Act 1877 |
E281261
|
entity |
| Predicate | legalRemedyType |
P13744
|
FINISHED |
| Object | specific performance |
—
|
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: specific performance | Statement: [Specific Relief Act 1877, legalRemedyType, specific performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRemedyType Context triple: [Specific Relief Act 1877, legalRemedyType, specific performance]
-
A.
remedySought
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
B.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
C.
typeOfJusticeMechanism
Indicates the kind or category of justice mechanism that characterizes how justice is pursued or administered in a given context.
-
D.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
E.
typeOfRemedy
chosen
Indicates that one entity is a specific kind or category of remedy in relation to another entity.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.