Triple

T3720161
Position Surface form Disambiguated ID Type / Status
Subject royal court of Judah E81619 entity
Predicate instanceOf P0 FINISHED
Object ancient Near Eastern court C1556 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: ancient Near Eastern court
Context triple: [royal court of Judah, instanceOf, ancient Near Eastern court]
  • A. ancient Near Eastern law collection
    An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
  • B. royal court chosen
    A royal court is the formal assembly of a monarch’s household, advisors, officials, and attendants who support, counsel, and ceremonially represent the sovereign’s authority and governance.
  • C. ancient Anatolian polities
    Ancient Anatolian polities were the diverse city-states, kingdoms, and empires that arose in the region of Anatolia (modern-day Turkey), including powers such as the Hittites, Lydians, Phrygians, and others, which played key roles in the political and cultural dynamics of the ancient Near East and Mediterranean.
  • D. imperial court office
    An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
  • E. court noble
    A court noble is a high-ranking aristocrat who serves in close proximity to a monarch or royal household, often holding ceremonial, advisory, or administrative roles within the court.
  • F. None of above.

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_69ad8b1b7ef081908d2d381bbf54985a completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 3:34 p.m.