Triple
T33113694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saul Tenser |
E847399
|
entity |
| Predicate | bodyModificationType |
P175108
|
FINISHED |
| Object | surgical performance art |
—
|
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: surgical performance art | Statement: [Saul Tenser, bodyModificationType, surgical performance art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyModificationType Context triple: [Saul Tenser, bodyModificationType, surgical performance art]
-
A.
bodyModificationReason
Indicates the reason or motivation behind a particular body modification performed on an entity.
-
B.
bodyTransformation
Indicates a change in an entity’s physical form, structure, or appearance into a different bodily state.
-
C.
bodyArt
chosen
Indicates that one entity has body art (such as tattoos, piercings, or similar modifications) applied to or present on another entity.
-
D.
bodyTreatment
Indicates a treatment or therapeutic procedure that is applied to a person's body.
-
E.
bodyPartsTransformedInto
Indicates that one or more body parts of an entity are changed or converted into different body parts or forms.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ecf6488190970a6852742adb14 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.