Triple
T9136640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Division of the Court of Appeal of England and Wales |
E219220
|
entity |
| Predicate | canHearAppealsOn |
P16126
|
FINISHED |
| Object | conviction |
—
|
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: conviction | Statement: [Criminal Division of the Court of Appeal of England and Wales, canHearAppealsOn, conviction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHearAppealsOn Context triple: [Criminal Division of the Court of Appeal of England and Wales, canHearAppealsOn, conviction]
-
A.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
B.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
C.
cannotHearCasesFrom
Indicates that one entity lacks the authority or ability to hear, consider, or adjudicate cases originating from another entity.
-
D.
hearsCasesUnder
chosen
Indicates that a judicial body or authority has the responsibility and power to adjudicate legal cases falling within a specified jurisdiction, category, or scope.
-
E.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8e1dc208190aafe501374ffe65c |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.