Triple

T8693484
Position Surface form Disambiguated ID Type / Status
Subject Exodus 23 E206347 entity
Predicate containsCondition P84224 FINISHED
Object Israel must obey the angel’s voice 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: Israel must obey the angel’s voice | Statement: [Exodus 23, containsCondition, Israel must obey the angel’s voice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsCondition
Context triple: [Exodus 23, containsCondition, Israel must obey the angel’s voice]
  • A. hasCondition
    Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
  • B. holdsUnderCondition
    Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
  • C. variableCondition
    Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
  • D. hasNumberOfConditions
    Indicates that an entity is associated with a specific count of conditions it has or is subject to.
  • E. definesConditionsFor
    Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69cc483f06f48190879f4702c8b4ed00 completed March 31, 2026, 10:18 p.m.
Created at: March 30, 2026, 6:33 p.m.