Triple

T11270267
Position Surface form Disambiguated ID Type / Status
Subject Taihō Code E266792 entity
Predicate influenced P9 FINISHED
Object Yōrō Code E266793 NE 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: Yōrō Code | Statement: [Taihō Code, influenced, Yōrō Code]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yōrō Code
Context triple: [Taihō Code, influenced, 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. Kodenmachō
    Kodenmachō is a neighborhood in Chūō ward, central Tokyo, known as a traditional commercial district with a mix of small businesses, offices, and residential buildings.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9506204819089dc0827483bd948 completed April 9, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f4229c7081909da6b22ee6bf4905 completed April 19, 2026, 3:26 p.m.
Created at: April 8, 2026, 9:31 p.m.