Triple

T16359946
Position Surface form Disambiguated ID Type / Status
Subject Solomon's Temple E397283 entity
Predicate builder P3143 FINISHED
Object King Solomon E4651 NE 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: King Solomon | Statement: [Solomon's Temple, builder, King Solomon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: King Solomon
Context triple: [Solomon's Temple, builder, King Solomon]
  • A. King Solomon chosen
    King Solomon is a biblical king of ancient Israel renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
  • B. Solomon
    Solomon is an Australian federal electoral division in the Northern Territory that includes the Darwin urban area and surrounding regions.
  • C. Solomon
    Solomon is a common Hebrew-origin surname borne by numerous individuals across diverse cultures and professions.
  • D. Solomon
    Solomon is a small city in Kansas, United States, known for its rural character and location spanning Dickinson and Saline counties.
  • E. Solomon
    Solomon is the given first name of the American conceptual artist and minimalist pioneer Sol LeWitt.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2fad241848190a9f32c7b050f20a5 completed April 18, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002dbce2508190b655de87f48e841e completed May 10, 2026, 7:03 a.m.
Created at: April 10, 2026, 5:07 a.m.