Triple
T31056791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Information Tribunal |
E791417
|
entity |
| Predicate | decisionSubjectToAppealTo |
P17875
|
FINISHED |
| Object | High Court of Justice |
E42491
|
NE 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: High Court of Justice | Statement: [Information Tribunal, decisionSubjectToAppealTo, High Court of Justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionSubjectToAppealTo Context triple: [Information Tribunal, decisionSubjectToAppealTo, High Court of Justice]
-
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.
decisionPublication
Indicates that a decision has been formally published or made publicly available.
-
D.
canBeAppealedTo
chosen
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
E.
requiresLeaveToAppeal
Indicates that a party must obtain formal permission from a higher court before proceeding with an appeal.
- F. None of above.
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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938a1cb288190b5e400a4ff4b64e4 |
completed | June 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 9 p.m.