Triple
T31056792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Information Tribunal |
E791417
|
entity |
| Predicate | decisionSubjectToAppealOn |
P173761
|
FINISHED |
| Object | point 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: point of law | Statement: [Information Tribunal, decisionSubjectToAppealOn, point of law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionSubjectToAppealOn Context triple: [Information Tribunal, decisionSubjectToAppealOn, point of law]
-
A.
decisionsSubjectTo
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
B.
reasonForAppealDecision
Indicates the justification or grounds cited for making a particular appeal decision.
-
C.
decisionHolding
Indicates that an entity has made, issued, or is responsible for a particular formal decision or ruling.
-
D.
requiresLeaveToAppeal
Indicates that a party must obtain formal permission from a higher court before proceeding with an appeal.
-
E.
cannotBeAppealed
Indicates that a decision, ruling, or outcome is final and cannot be challenged or reviewed through an appeal process.
- F. None of above. chosen
Provenance (4 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 29, 2026, 9 p.m.