Triple

T6295764
Position Surface form Disambiguated ID Type / Status
Subject Constitution of 17 May 1814 E141126 entity
Predicate rankInLegalHierarchy P6053 FINISHED
Object supreme law of Norway 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: supreme law of Norway | Statement: [Constitution of 17 May 1814, rankInLegalHierarchy, supreme law of Norway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankInLegalHierarchy
Context triple: [Constitution of 17 May 1814, rankInLegalHierarchy, supreme law of Norway]
  • A. legalHierarchyRank chosen
    Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
  • B. courtRank
    Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
  • C. hasLegalHierarchy
    Indicates that one entity holds a higher or subordinate legal status, authority, or jurisdiction in relation to another within a formal legal structure.
  • D. hasLegalRank
    Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
  • E. legalAuthorityLevel
    Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within 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_69c008cdf2ac8190bb640c94478fb4ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06439a6908190b0a8ebf426d3ca02 completed March 22, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69c060df0d8881908215575862ef6831 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:27 p.m.