Triple

T20257886
Position Surface form Disambiguated ID Type / Status
Subject Mahan confederacy E498751 entity
Predicate memberPolities P139424 FINISHED
Object multiple small chiefdoms 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: multiple small chiefdoms | Statement: [Mahan confederacy, memberPolities, multiple small chiefdoms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: memberPolities
Context triple: [Mahan confederacy, memberPolities, multiple small chiefdoms]
  • A. linkedPolities
    Indicates that two political entities are connected by some defined relationship, such as alliance, dependency, or shared governance.
  • B. politicalEntityConstrained
    Indicates that a political entity is subject to limitations, restrictions, or control imposed by another actor, rule, or condition.
  • C. hasPolity
    Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
  • D. politicalEntityWithin
    Indicates that one political entity is geographically or administratively contained within another political entity.
  • E. memberStatesOrganization
    Indicates that an organization is composed of, or includes as members, the specified states.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674c7296c819092860942de8f28d5 completed April 20, 2026, 6:47 p.m.
PD Predicate disambiguation batch_69e55b1b23f88190bdcbe2f81dd226dd completed April 19, 2026, 10:45 p.m.
PDg Predicate description generation batch_69e56702ad04819099c1c08f28d16809 completed April 19, 2026, 11:36 p.m.
Created at: April 11, 2026, 11:41 p.m.