Triple

T21461880
Position Surface form Disambiguated ID Type / Status
Subject Nakatsu Castle E529490 entity
Predicate regionHistoricRole P29914 FINISHED
Object strategic stronghold in northern Kyushu 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: strategic stronghold in northern Kyushu | Statement: [Nakatsu Castle, regionHistoricRole, strategic stronghold in northern Kyushu]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionHistoricRole
Context triple: [Nakatsu Castle, regionHistoricRole, strategic stronghold in northern Kyushu]
  • A. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
  • B. regionHistory
    Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
  • C. regionHistoricalName
    Indicates that a region has been known by a particular historical name during some past period.
  • D. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • E. roleHistoricallyAssociatedWith
    Indicates that one role, position, or function has been historically linked or commonly associated with another entity, role, or context over time.
  • 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_69e0c458133481908ae8b41a12c4edec completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9ef0c0881908554977df00604a6 completed April 23, 2026, 9:44 a.m.
PD Predicate disambiguation batch_69e631df1b38819088d3604854e697b4 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:09 p.m.