Triple

T26740632
Position Surface form Disambiguated ID Type / Status
Subject Fukushima Masanori E674241 entity
Predicate reasonForLossOfDomain P175304 FINISHED
Object violations of Tokugawa regulations on castle repairs 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: violations of Tokugawa regulations on castle repairs | Statement: [Fukushima Masanori, reasonForLossOfDomain, violations of Tokugawa regulations on castle repairs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForLossOfDomain
Context triple: [Fukushima Masanori, reasonForLossOfDomain, violations of Tokugawa regulations on castle repairs]
  • A. reasonForContactLoss
    Indicates the cause or circumstance that led to the loss or termination of contact between entities.
  • B. lostStatusReason
    Indicates the reason or cause for which something transitioned into a lost or unsuccessful status.
  • C. reasonForLossOfSuccessionRights
    Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
  • D. causedLossOf
    Indicates that one entity brought about or was responsible for another entity experiencing a loss.
  • E. reasonForLossOfVote
    Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
  • F. None of above. chosen

Provenance (4 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_69eecda63a3881908095c47900692e65 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6d1d916f881909575c2b22c416a5b completed May 3, 2026, 4:40 a.m.
PD Predicate disambiguation batch_69f6cfe2183481908ae4e85a59c66f69 completed May 3, 2026, 4:32 a.m.
PDg Predicate description generation batch_69f6d0d331dc8190be5aa6bfc6365e67 completed May 3, 2026, 4:36 a.m.
Created at: April 27, 2026, 3:49 a.m.