Triple
T1000771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Bowls |
E21596
|
entity |
| Predicate | firstBowlEffect |
P1634
|
FINISHED |
| Object | painful sores on those with the mark of the beast |
—
|
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: painful sores on those with the mark of the beast | Statement: [Seven Bowls, firstBowlEffect, painful sores on those with the mark of the beast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBowlEffect Context triple: [Seven Bowls, firstBowlEffect, painful sores on those with the mark of the beast]
-
A.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
B.
firstSuccessfulImpactBy
Indicates that one entity is the earliest or initial successful impactor upon another entity in a given context or sequence of events.
-
C.
primaryEffect
chosen
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
D.
firstGamePlayed
Indicates the specific game that an entity participated in before any other, marking the earliest game in which it played.
-
E.
givesFirstPickTo
Indicates that one entity grants another entity the right to choose first among available options.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.