Triple
T26038101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Court of Appeal |
E647608
|
entity |
| Predicate | decisionCanBeSubjectTo |
P15229
|
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: [Paris Court of Appeal, decisionCanBeSubjectTo, appeal in cassation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionCanBeSubjectTo Context triple: [Paris Court of Appeal, decisionCanBeSubjectTo, appeal in cassation]
-
A.
decisionEnforceableIn
Indicates that a particular decision is legally valid and can be executed or enforced within a specified jurisdiction or context.
-
B.
decisionsSubjectTo
chosen
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
C.
decisionEnforcement
Indicates that an authority or mechanism compels compliance with, or carries out, a previously made decision or ruling.
-
D.
decisionHolding
Indicates that an entity has made, issued, or is responsible for a particular formal decision or ruling.
-
E.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061fd954819082000e723287e423 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:08 a.m.