Triple
T17485106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Peter |
E425758
|
entity |
| Predicate | traditionallyCrucifiedUpsideDown |
P40222
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Saint Peter, traditionallyCrucifiedUpsideDown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyCrucifiedUpsideDown Context triple: [Saint Peter, traditionallyCrucifiedUpsideDown, true]
-
A.
crucifiedOn
Indicates that one entity was executed by crucifixion upon or using another entity (typically a cross or similar structure).
-
B.
traditionallyMartyredWith
chosen
Indicates that an entity is customarily believed or depicted to have been martyred using a particular method, instrument, or circumstance.
-
C.
dateCrucifixions
Indicates that one entity specifies or records the date on which another entity was crucified.
-
D.
notCrucifiedAccordingToIslam
Indicates that, according to Islamic belief or doctrine, the referenced individual was not actually crucified.
-
E.
victimOfExecutionBy
Indicates that one entity was executed as a result of an execution carried out by another entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d13e208190a187b5a08fd2b5d5 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.