Triple

T8693485
Position Surface form Disambiguated ID Type / Status
Subject Exodus 23 E206347 entity
Predicate containsWarning P20086 FINISHED
Object do not bow down to the gods of the nations LITERAL 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: do not bow down to the gods of the nations | Statement: [Exodus 23, containsWarning, do not bow down to the gods of the nations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsWarning
Context triple: [Exodus 23, containsWarning, do not bow down to the gods of the nations]
  • A. warnsAbout
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • B. warningIssued
    Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
  • C. warnedWith chosen
    Indicates that one entity issued a warning to another entity using or accompanied by a particular medium, content, or instrument.
  • D. hasHealthWarningOnPackaging
    Indicates that an item’s packaging displays a health-related warning message or symbol.
  • E. warningType
    Indicates the specific category or classification of a warning associated with an entity or event.
  • F. None of above.

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_69ca835481fc819084e33d3bc883bfa6 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5826bbb48190a212fb1bb06e05e6 completed March 31, 2026, 11:26 p.m.
PD Predicate disambiguation batch_69cc4569f9048190b9c86b4c81103d35 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:33 p.m.