Triple

T4922372
Position Surface form Disambiguated ID Type / Status
Subject Hosea E110494 entity
Predicate symbolicAction P16925 FINISHED
Object marriage to an unfaithful wife as prophetic sign 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: marriage to an unfaithful wife as prophetic sign | Statement: [Hosea, symbolicAction, marriage to an unfaithful wife as prophetic sign]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: symbolicAction
Context triple: [Hosea, symbolicAction, marriage to an unfaithful wife as prophetic sign]
  • A. symbolicAbility
    Indicates the capacity of an entity to understand, manipulate, or use symbols to represent concepts, objects, or relationships.
  • B. containsSymbolicAct chosen
    Indicates that one entity includes or incorporates a symbolic action or gesture associated with another entity.
  • C. actsOn
    Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
  • D. fromAct
    Indicates that an entity originates from, is produced by, or results from a specified action or event.
  • E. speechAct
    Indicates that one entity performs a communicative action (such as stating, asking, commanding, or promising) directed toward another entity or audience.
  • 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_69bd4413f9908190afcff44d7929cc4c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ffc2ab08190992db2400562bcee completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c3421588190ab08e92b9558042e completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:30 p.m.