Triple
T5839084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of cassation |
E129546
|
entity |
| Predicate | legalRemedyName |
P7077
|
FINISHED |
| Object | appeal in cassation |
—
|
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: appeal in cassation | Statement: [court of cassation, legalRemedyName, appeal in cassation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRemedyName Context triple: [court of cassation, legalRemedyName, appeal in cassation]
-
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.
typeOfJusticeMechanism
Indicates the kind or category of justice mechanism that characterizes how justice is pursued or administered in a given context.
-
C.
legalProcedureUsed
chosen
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
D.
popularNameOfLawAtIssue
Indicates the commonly used or well-known name by which the law in question is referred to.
-
E.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.