Triple

T29368495
Position Surface form Disambiguated ID Type / Status
Subject Hikone E744784 entity
Predicate hasFeudalDomainHistory P53604 FINISHED
Object Hikone Domain NE NERFINISHED

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: Hikone Domain | Statement: [Hikone, hasFeudalDomainHistory, Hikone Domain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeudalDomainHistory
Context triple: [Hikone, hasFeudalDomainHistory, Hikone Domain]
  • A. hasFeudalOverlord
    Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
  • B. isFeudalState
    Indicates that a political entity operates under a feudal system, where power is decentralized and structured through hierarchical obligations between lords and vassals.
  • C. isFeudal
    Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
  • D. hadFeudalSystem
    Indicates that a society, region, or polity operated under a feudal system of hierarchical landholding and obligations between lords and vassals.
  • E. hasHistoricalPolity chosen
    Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
  • 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_69f0a79ba954819094597628112c6091 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f6cee45590819086e489bfccbe4ac3 completed May 3, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69f6cc1188708190b8f0f56e595e6057 completed May 3, 2026, 4:16 a.m.
Created at: April 28, 2026, 2:25 p.m.