Triple

T51618
Position Surface form Disambiguated ID Type / Status
Subject Judiciary of Japan E1012 entity
Predicate legalSystemType P605 FINISHED
Object civil law system 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: civil law system | Statement: [Judiciary of Japan, legalSystemType, civil law system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalSystemType
Context triple: [Judiciary of Japan, legalSystemType, civil law system]
  • 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. legalContext
    Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
  • C. constitutionalDomain
    Indicates that something falls within the scope, authority, or subject matter defined or governed by a particular constitution.
  • D. legalSubject
    Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
  • E. legalForm
    Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
  • 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_69a2480baefc81909951b14058479aa2 completed Feb. 28, 2026, 1:42 a.m.
NER Named-entity recognition batch_69a24ba7016481909d595402712db6e2 completed Feb. 28, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69a24ac23f04819080cef9365ed990d4 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:47 a.m.