Triple

T3723256
Position Surface form Disambiguated ID Type / Status
Subject Joel E81687 entity
Predicate hasComponent P35 FINISHED
Object Yo (Yahweh) E108211 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: Yo (Yahweh) | Statement: [Joel, hasComponent, Yo (Yahweh)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yo (Yahweh)
Context triple: [Joel, hasComponent, Yo (Yahweh)]
  • A. YHWH chosen
    YHWH is the personal name of the God of Israel in the Hebrew Bible, regarded as the supreme, covenant-making and covenant-keeping deity in Jewish and Christian traditions.
  • B. חַוָּה
    חַוָּה is the Hebrew name of Eve, the first woman in the biblical creation narrative in the Book of Genesis.
  • C. Shaddai
    Shaddai is a Hebrew name for God, often associated with divine protection and power in Jewish tradition.
  • D. Nyame
    Nyame is the supreme sky god and creator in Akan religion, associated with the sun, rain, and the ordering of the universe.
  • E. Sumu-la-El
    Sumu-la-El was an early Amorite king of Babylon known for consolidating and expanding the city-state into a significant regional power.
  • 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_69ad8b1b7ef081908d2d381bbf54985a completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcaf3f2ec8190a3a8f363cfb762f3 completed March 8, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4db0e40b08190abacdda42dbde411 completed March 14, 2026, 3:50 a.m.
Created at: March 8, 2026, 3:34 p.m.