Triple

T32636614
Position Surface form Disambiguated ID Type / Status
Subject Lotan E834359 entity
Predicate defeatSignificance P137024 FINISHED
Object establishment of divine kingship of Baal 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: establishment of divine kingship of Baal | Statement: [Lotan, defeatSignificance, establishment of divine kingship of Baal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defeatSignificance
Context triple: [Lotan, defeatSignificance, establishment of divine kingship of Baal]
  • A. defeatSymbolizes chosen
    Indicates that an instance of defeat is used to symbolically represent or stand for another concept, state, or idea.
  • B. defeatEffect
    Indicates that one entity’s defeat causes a particular outcome or change to occur for another entity or the overall situation.
  • C. defeat
    Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
  • D. defeatAttributedTo
    Indicates that one entity’s defeat is causally attributed to the actions, influence, or presence of another entity.
  • E. significantDefeat
    Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
  • 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_69f3492dc2308190a88c6e30a3f3f576 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c775d6188190b236fc4f89a11b61 completed May 3, 2026, 3:56 a.m.
PD Predicate disambiguation batch_69f6c3f617c08190a70ba880210f908c completed May 3, 2026, 3:41 a.m.
Created at: May 1, 2026, 1:07 a.m.