Triple

T4118820
Position Surface form Disambiguated ID Type / Status
Subject Doctrine of Right E90359 entity
Predicate hasKeyDistinction P18160 FINISHED
Object innate right versus acquired right 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: innate right versus acquired right | Statement: [Doctrine of Right, hasKeyDistinction, innate right versus acquired right]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKeyDistinction
Context triple: [Doctrine of Right, hasKeyDistinction, innate right versus acquired right]
  • A. hasDistinctFeature chosen
    Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
  • B. hasRegisterDistinction
    Indicates that there is a meaningful difference in language register (e.g., formality or style) between the related linguistic forms or usages.
  • C. hasDistinctHierarchy
    Indicates that one entity is organized under a hierarchical structure that is clearly separate and non-overlapping from another entity’s hierarchy.
  • D. hasDistinctIdentity
    Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
  • E. hasDistinctSetFor
    Indicates that one entity is associated with a separate, non-overlapping collection of items or elements specifically designated for another entity.
  • 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_69aed95c080881908125e30c5dcdc6f8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0246e40081908ad6741a830ca68e completed March 9, 2026, 5:24 p.m.
PD Predicate disambiguation batch_69af01867698819098e4144634b2ec4f completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:41 p.m.