Triple

T142744
Position Surface form Disambiguated ID Type / Status
Subject British Empire E2886 entity
Predicate legalLegacy P605 FINISHED
Object common law 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: common law | Statement: [British Empire, legalLegacy, common law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalLegacy
Context triple: [British Empire, legalLegacy, common law]
  • A. legalCase
    Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
  • B. legalDoctrine
    Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
  • C. 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.
  • D. 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.
  • E. legalSubject
    Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or 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_69a2521e35c08190b28e5c9f1e3c9b59 completed Feb. 28, 2026, 2:25 a.m.
NER Named-entity recognition batch_69a2580ca15481909fa3e87d804a1b23 completed Feb. 28, 2026, 2:50 a.m.
PD Predicate disambiguation batch_69a2565559ac81909e0c4e095a7dfa27 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:31 a.m.