Triple
T30403465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jochanaan |
E773412
|
entity |
| Predicate | dramaticConsequenceOfRejection |
P72727
|
FINISHED |
| Object | Salome’s demand for his head |
—
|
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: Salome’s demand for his head | Statement: [Jochanaan, dramaticConsequenceOfRejection, Salome’s demand for his head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticConsequenceOfRejection Context triple: [Jochanaan, dramaticConsequenceOfRejection, Salome’s demand for his head]
-
A.
communityPunishedForRejection
Indicates that a community is subjected to punishment as a consequence of rejecting or refusing something (such as a message, offer, or authority).
-
B.
resultOfDenial
Indicates that something occurs or exists as a consequence of a prior denial event or refusal.
-
C.
resultOfRejection
chosen
Indicates that something occurs as a consequence or outcome of a prior act of rejection.
-
D.
denialConsidered
Indicates that a denial or rejection of something has been evaluated or taken into account in a decision or reasoning process.
-
E.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861c95e88190a5f3a4a6c952692a |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.