Triple

T17688410
Position Surface form Disambiguated ID Type / Status
Subject Sadaijin E440957 entity
Predicate legalBasis P125 FINISHED
Object Yōrō Code NE NERFINISHED

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: Yōrō Code | Statement: [Sadaijin, legalBasis, Yōrō Code]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yōrō Code
Context triple: [Sadaijin, legalBasis, Yōrō Code]
  • A. Yōrō Code chosen
    Yōrō Code was a major 8th-century Japanese ritsuryō legal and administrative code that systematized government structure and social regulations during the Nara period.
  • B. Asuka Kiyomihara Code
    The Asuka Kiyomihara Code was an early Japanese legal code established in the late 7th century that laid the groundwork for the later ritsuryō system of centralized imperial governance.
  • C. Taihō Code
    The Taihō Code was an early 8th-century Japanese legal and administrative code that helped establish a centralized, bureaucratic state modeled on Chinese systems during the Nara period.
  • D. M-Code
    M-Code is an advanced, encrypted military GPS signal designed to provide more secure and jam-resistant positioning and navigation for authorized users.
  • E. Kode
    Kode is a music producer known for crafting high-impact tracks for prominent artists in the Superstar music scene.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4704944d8819089b153aa14839fc0 completed April 19, 2026, 6:03 a.m.
Created at: April 10, 2026, 10:03 a.m.