Triple
T31972520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Judicature |
E816352
|
entity |
| Predicate | mergedCourtsOf |
P173068
|
FINISHED |
| Object | common law |
—
|
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: common law | Statement: [Supreme Court of Judicature, mergedCourtsOf, common law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedCourtsOf Context triple: [Supreme Court of Judicature, mergedCourtsOf, common law]
-
A.
consolidatedJurisdictionOf
Indicates that legal authority or control over multiple areas or cases has been combined and is exercised under a single jurisdiction.
-
B.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
C.
parallelCourt
Indicates that two legal proceedings or courts are operating at the same time on related or comparable matters, without one being hierarchically superior to the other.
-
D.
hasCourtInEach
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
E.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
- F. None of above. chosen
Provenance (4 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:10 a.m.