Triple

T21685013
Position Surface form Disambiguated ID Type / Status
Subject 長門国豊浦郡下関 E535206 entity
Predicate 行政区分上の変遷 P62719 FINISHED
Object 近代以降は山口県下関市の一部となる 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: 近代以降は山口県下関市の一部となる | Statement: [長門国豊浦郡下関, 行政区分上の変遷, 近代以降は山口県下関市の一部となる]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 行政区分上の変遷
Context triple: [長門国豊浦郡下関, 行政区分上の変遷, 近代以降は山口県下関市の一部となる]
  • A. partOfAdministrativeDivisionReform
    Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
  • B. hasTerritoryReorganizedInto
    Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
  • C. territorialChange
    Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
  • D. historicalCountyChange chosen
    Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
  • E. administrativeCenterMovedFrom
    Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location to another.
  • 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_69e0c469b6ec8190aee4cadd1527db91 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef96ca668481909f53853c7a8ea811 completed April 27, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69e6968abfdc81909cf9e0bd72db9eca completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:44 p.m.