Triple
T6378384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown copyright |
E143520
|
entity |
| Predicate | existsInLegalSystem |
P65627
|
FINISHED |
| Object | common law jurisdictions |
—
|
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 jurisdictions | Statement: [Crown copyright, existsInLegalSystem, common law jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsInLegalSystem Context triple: [Crown copyright, existsInLegalSystem, common law jurisdictions]
-
A.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
B.
hasLegalSystemType
chosen
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
C.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
D.
partOfLegalSystem
Indicates that something belongs to, is included within, or functions as a component of a particular legal system.
-
E.
separateLegalSystem
Indicates that one entity maintains its own distinct and independent legal system from another entity.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683ed0788190b00f626c76a71ea2 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.