Triple
T19074473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Judas |
E466868
|
entity |
| Predicate | portraysCrucifixionAs |
P134217
|
FINISHED |
| Object | necessary for salvation plan |
—
|
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: necessary for salvation plan | Statement: [Gospel of Judas, portraysCrucifixionAs, necessary for salvation plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysCrucifixionAs Context triple: [Gospel of Judas, portraysCrucifixionAs, necessary for salvation plan]
-
A.
crucifiedOn
Indicates that one entity was executed by crucifixion upon or using another entity (typically a cross or similar structure).
-
B.
portraysReligionAs
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
-
C.
viewOnMartyrdom
Indicates a stance or perspective that an entity holds regarding the concept, value, or justification of martyrdom.
-
D.
tookTheCross
Indicates that a person formally committed to participate in a crusade or holy war, typically by taking a religious vow or symbol.
-
E.
dateCrucifixions
Indicates that one entity specifies or records the date on which another entity was crucified.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e2ccbc8190bf5a2da915c81a03 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.