Triple
T27700477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Assizes |
E698413
|
entity |
| Predicate | heardCasesOf |
P16126
|
FINISHED |
| Object | felonies |
—
|
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: felonies | Statement: [York Assizes, heardCasesOf, felonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heardCasesOf Context triple: [York Assizes, heardCasesOf, felonies]
-
A.
hearCasesBroughtBy
Indicates that a judicial body or authority formally considers and adjudicates legal cases initiated by a particular party or group.
-
B.
hearsCasesAgainst
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
-
C.
hearsCasesAs
Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
-
D.
hearsCasesWith
Indicates that one judicial body or judge conducts proceedings together with another judicial body or judge in hearing the same cases.
-
E.
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.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.