Triple
T30645539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots Law Times |
E780108
|
entity |
| Predicate | legalSystemCovered |
P605
|
FINISHED |
| Object | Scots 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: Scots law | Statement: [Scots Law Times, legalSystemCovered, Scots law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSystemCovered Context triple: [Scots Law Times, legalSystemCovered, Scots law]
-
A.
legalSystem
chosen
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
B.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
C.
legalSystemDepictedAs
Indicates that one entity portrays, represents, or characterizes a legal system in a particular way or form.
-
D.
legalSystemWorkedIn
Indicates that a person carried out their professional legal activities within a particular legal system or jurisdiction.
-
E.
legalProtectionJurisdiction
Indicates the jurisdiction or legal authority under which an entity is granted legal protection.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 29, 2026, 8:29 p.m.