Triple
T31466439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immigration Act 2009 |
E802730
|
entity |
| Predicate | tribunalReplaced |
P171913
|
FINISHED |
| Object | Removal Review Authority |
—
|
NE NERFINISHED |
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: Removal Review Authority | Statement: [Immigration Act 2009, tribunalReplaced, Removal Review Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribunalReplaced Context triple: [Immigration Act 2009, tribunalReplaced, Removal Review Authority]
-
A.
tribunalFound
Indicates that a tribunal has formally determined or concluded something regarding a case or matter.
-
B.
tribunalConstitutedBy
Indicates that a tribunal is formed, established, or composed by a specified authority, body, or set of members.
-
C.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
D.
tribunalNumber
Indicates the identifying number assigned to a specific tribunal within a legal or administrative system.
-
E.
typeOfTribunal
Indicates the specific category or kind of tribunal (e.g., court or adjudicative body) to which an entity belongs.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:23 p.m.