Triple
T17016251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Court at Newcastle upon Tyne |
E412827
|
entity |
| Predicate | typicalJudges |
P27690
|
FINISHED |
| Object | High Court judges |
—
|
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: High Court judges | Statement: [Crown Court at Newcastle upon Tyne, typicalJudges, High Court judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalJudges Context triple: [Crown Court at Newcastle upon Tyne, typicalJudges, High Court judges]
-
A.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
-
B.
styleOfJudges
Indicates the characteristic manner or approach that judges use when performing their judging role.
-
C.
judgesMayBe
chosen
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
-
D.
judgesTerm
Indicates that one entity formally evaluates or makes a judgment about a specific term or expression.
-
E.
roleInJudges
Indicates that an entity holds or held a specific role, position, or function within a judicial body or among a group of judges.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d47fec248190bf261cac920291b1 |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.