Triple
T1151782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belshazzar |
E23691
|
entity |
| Predicate | offense |
P26122
|
FINISHED |
| Object | profaning sacred vessels from the Temple in Jerusalem |
—
|
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: profaning sacred vessels from the Temple in Jerusalem | Statement: [Belshazzar, offense, profaning sacred vessels from the Temple in Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offense Context triple: [Belshazzar, offense, profaning sacred vessels from the Temple in Jerusalem]
-
A.
offenseNicknamed
Indicates that an offensive unit, team, or strategy is commonly referred to by a particular nickname.
-
B.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
-
C.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.