Triple

T17666182
Position Surface form Disambiguated ID Type / Status
Subject Article 17 of the Constitution of Japan E440387 entity
Predicate enforceableThrough P100294 FINISHED
Object Japanese courts 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: Japanese courts | Statement: [Article 17 of the Constitution of Japan, enforceableThrough, Japanese courts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: enforceableThrough
Context triple: [Article 17 of the Constitution of Japan, enforceableThrough, Japanese courts]
  • A. enforcedOn
    Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
  • B. appliesLawThrough chosen
    Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
  • C. hasLegalForceAs
    Indicates that one thing possesses the binding legal effect or validity in the capacity or role of another specified thing.
  • D. hasLegalForceIn
    Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
  • E. enforcementStrength
    Indicates the degree or intensity with which rules, laws, or policies are applied and enforced in a given context.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46ea9d91c81908414ef38c7fb36a4 completed April 19, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69e3cde007d8819090dd92eea9f022cc completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 9:57 a.m.