Triple
T968063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burial of Jesus |
E20880
|
entity |
| Predicate | mentionedInCreedPhrase |
P22503
|
FINISHED |
| Object | “was crucified, died, and was buried” |
—
|
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: “was crucified, died, and was buried” | Statement: [Burial of Jesus, mentionedInCreedPhrase, “was crucified, died, and was buried”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInCreedPhrase Context triple: [Burial of Jesus, mentionedInCreedPhrase, “was crucified, died, and was buried”]
-
A.
recognizesCreed
Indicates that one entity formally accepts or acknowledges the religious or ideological creed of another entity.
-
B.
creed
Indicates that an entity holds or is associated with a particular system of religious or ideological belief.
-
C.
religiousPhraseOptional
Indicates that a religious phrase may be present in the context but is not required.
-
D.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
E.
relationToOtherCreeds
Indicates how one belief system, doctrine, or creed is positioned or related in comparison to other creeds.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43549008190a4d65efdc3bda520 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.