Triple
T30644944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Division of the Court of Appeal |
E780094
|
entity |
| Predicate | appealsOn |
P15240
|
FINISHED |
| Object | points of 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: points of law | Statement: [Civil Division of the Court of Appeal, appealsOn, points of law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealsOn Context triple: [Civil Division of the Court of Appeal, appealsOn, points of law]
-
A.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
B.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
C.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
D.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
E.
typeOfAppeals
chosen
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 29, 2026, 8:29 p.m.