Triple
T2669369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guernsey Legal French |
E55712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman-based legal jargon |
C9504
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Norman-based legal jargon Context triple: [Guernsey Legal French, instanceOf, Norman-based legal jargon]
-
A.
Norman
Norman is a conceptual class representing an individual person characterized by specific attributes (such as name, age, and occupation) and behaviors (such as communicating, working, and interacting with other entities) within a given domain.
-
B.
legal doctrine
A legal doctrine is a principle or framework developed through statutes, judicial decisions, and scholarly interpretation that guides how laws are understood, applied, and evolved in legal systems.
-
C.
British colonial law
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
-
D.
medieval law
chosen
Medieval law is the body of legal customs, codes, and practices that governed social, economic, and political life in Europe during the Middle Ages, blending local traditions, feudal obligations, royal decrees, and canon (church) law.
-
E.
civil law tradition
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
- F. None of above.
Provenance (1 batch)
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.