Triple
T2398165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadducees |
E47698
|
entity |
| Predicate | positionOnAfterlife |
P11074
|
FINISHED |
| Object | denied afterlife rewards and punishments |
—
|
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: denied afterlife rewards and punishments | Statement: [Sadducees, positionOnAfterlife, denied afterlife rewards and punishments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnAfterlife Context triple: [Sadducees, positionOnAfterlife, denied afterlife rewards and punishments]
-
A.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
B.
hasViewOnAfterlife
chosen
Indicates that an entity holds a particular belief, opinion, or perspective regarding the nature of the afterlife.
-
C.
residenceAfterDeath
Indicates the location where an individual is said to reside or be located after their death.
-
D.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
E.
positionInPantheon
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c5f0948190b4ea729693d8c306 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.