Triple

T20054899
Position Surface form Disambiguated ID Type / Status
Subject Chileab E499301 entity
Predicate sibling P363 FINISHED
Object Solomon 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: Solomon | Statement: [Chileab, sibling, Solomon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solomon
Context triple: [Chileab, sibling, Solomon]
  • A. Solomon
    Solomon is a character in Min Jin Lee's novel "Pachinko," depicted as a third-generation Korean-Japanese man navigating questions of identity, family legacy, and discrimination in postwar Japan.
  • B. Solomon
    Solomon is the given first name of the American conceptual artist and minimalist pioneer Sol LeWitt.
  • C. Solomon
    Solomon is a small city in Kansas, United States, known for its rural character and location spanning Dickinson and Saline counties.
  • D. Solomon
    Solomon is a common Hebrew-origin surname borne by numerous individuals across diverse cultures and professions.
  • E. Solomon chosen
    Solomon is a biblical king of ancient Israel renowned for his wisdom, wealth, and monumental building projects, including the First Temple in Jerusalem.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66332b300819097f5dca1636e5822 completed April 20, 2026, 5:32 p.m.
Created at: April 11, 2026, 3:38 p.m.