Triple

T3160123
Position Surface form Disambiguated ID Type / Status
Subject Salome E66081 entity
Predicate rewardForDance P31175 FINISHED
Object any request promised by Herod Antipas 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: any request promised by Herod Antipas | Statement: [Salome, rewardForDance, any request promised by Herod Antipas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rewardForDance
Context triple: [Salome, rewardForDance, any request promised by Herod Antipas]
  • A. rewardFulfilledFor
    Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
  • B. rewardSignal
    Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
  • C. rewardUse
    Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
  • D. grantedAsRewardFor chosen
    Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
  • E. winnerReceives
    Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
  • 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_69ad85850c1481908a9e9c6242238de2 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada61606bc8190a8ad760d680924eb completed March 8, 2026, 4:38 p.m.
PD Predicate disambiguation batch_69ad9dfe0a948190928f2201d671c654 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:05 p.m.