Triple
T26153881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Committee of the House of Lords |
E659903
|
entity |
| Predicate | decidedAppealsFrom |
P160727
|
FINISHED |
| Object | Court of Session |
—
|
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: Court of Session | Statement: [Judicial Committee of the House of Lords, decidedAppealsFrom, Court of Session]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidedAppealsFrom Context triple: [Judicial Committee of the House of Lords, decidedAppealsFrom, Court of Session]
-
A.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
B.
decisionsCalled
Indicates that one entity has made or issued formal decisions that are referred to or invoked by another entity.
-
C.
decidedMatters
Indicates that one entity has formally resolved, determined, or settled specific issues or questions concerning another entity.
-
D.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
E.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0d35288190b016726366d3ad27 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 26, 2026, 8:26 p.m.