Triple

T3263427
Position Surface form Disambiguated ID Type / Status
Subject Herod Philip E68466 entity
Predicate instanceOf P0 FINISHED
Object Roman client ruler C12572 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: Roman client ruler
Context triple: [Herod Philip, instanceOf, Roman client ruler]
  • A. Western Roman emperor
    A Western Roman emperor is the sovereign ruler of the western half of the Roman Empire, holding supreme political, military, and religious authority from the late 3rd to the late 5th century CE.
  • B. client state of the Roman Empire
    A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
  • C. Eastern Roman emperor
    An Eastern Roman emperor is the sovereign ruler of the eastern portion of the Roman Empire, later known as the Byzantine Empire, wielding supreme political, military, and religious authority.
  • D. 4th-century Roman emperor
    A 4th-century Roman emperor is a sovereign ruler of the Roman Empire during the 300s CE, navigating military, religious, and administrative transformations that reshaped the ancient Mediterranean world.
  • E. Roman aristocrat
    A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political influence, owns extensive land and slaves, and upholds traditional social and cultural norms of the elite.
  • F. None of above. chosen

Provenance (1 batch)

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_69ad8590444081909e8107a8aeef3a23 completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:09 p.m.