Triple

T23673845
Position Surface form Disambiguated ID Type / Status
Subject Shimazu clan lords of Satsuma Domain E584811 entity
Predicate statusUnderTokugawa P118082 FINISHED
Object semi-autonomous tozama domain 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: semi-autonomous tozama domain | Statement: [Shimazu clan lords of Satsuma Domain, statusUnderTokugawa, semi-autonomous tozama domain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusUnderTokugawa
Context triple: [Shimazu clan lords of Satsuma Domain, statusUnderTokugawa, semi-autonomous tozama domain]
  • A. shogunateName
    Indicates the name assigned to a particular shogunate.
  • B. preMeijiStatus chosen
    Indicates the status or condition an entity held prior to the Meiji period, typically in contrast to its later or modern status.
  • C. administrativeStatusDuringJapaneseRule
    Indicates the administrative status or classification an entity held under Japanese colonial rule during the specified period.
  • D. roleInMeijiRestoration
    Indicates the specific part, function, or contribution an entity had in bringing about or shaping the Meiji Restoration.
  • E. roleInEdoPeriod
    Indicates that an entity held a specific role, position, or function during Japan’s Edo period.
  • 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_69e24901421881908c17a5293bdd4a8e completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b4f1dee08190bfe78564c65f01ad completed April 29, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f118dd13008190a8799b4e9cadbd79 completed April 28, 2026, 8:30 p.m.
Created at: April 17, 2026, 6:51 p.m.