Triple
T30644956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Division of the Court of Appeal |
E780094
|
entity |
| Predicate | doesNotHear |
P4300
|
FINISHED |
| Object | criminal appeals |
—
|
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: criminal appeals | Statement: [Civil Division of the Court of Appeal, doesNotHear, criminal appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotHear Context triple: [Civil Division of the Court of Appeal, doesNotHear, criminal appeals]
-
A.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
B.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
C.
hearsFor
Indicates that one entity perceives or listens to sounds, speech, or signals on behalf of, or in place of, another entity.
-
D.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
E.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:29 p.m.