Triple
T32226250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Ernest Ryder |
E823210
|
entity |
| Predicate | divisionOfHighCourt |
P47013
|
FINISHED |
| Object | Family Division |
—
|
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: Family Division | Statement: [Sir Ernest Ryder, divisionOfHighCourt, Family Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionOfHighCourt Context triple: [Sir Ernest Ryder, divisionOfHighCourt, Family Division]
-
A.
originalJurisdictionOfHighCourt
Indicates that a particular matter or case falls within the High Court’s original jurisdiction to hear and decide it as a court of first instance.
-
B.
highCourtWithJurisdiction
Indicates that a specified high court holds legal authority and jurisdiction over a particular area, case type, or entity.
-
C.
hasCourtDivision
chosen
Indicates that a court is organized into, or belongs to, a specific internal division or section within the judicial system.
-
D.
highCourtSeat
Indicates that a location serves as the official seat or headquarters of a high court.
-
E.
highCourtBench
Indicates that a particular bench or panel of judges belongs to, or is constituted within, a high court.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbcbd31c8190a482a5fd5040410d |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.