Triple
T29692523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull 5 |
E751247
|
entity |
| Predicate | preservationDetail |
P9592
|
FINISHED |
| Object | minimal postmortem distortion |
—
|
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: minimal postmortem distortion | Statement: [Skull 5, preservationDetail, minimal postmortem distortion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservationDetail Context triple: [Skull 5, preservationDetail, minimal postmortem distortion]
-
A.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
-
B.
preservationMethod
Indicates the technique or process used to maintain, protect, or prolong the condition, quality, or usability of something over time.
-
C.
preservationFocus
Indicates that the primary concern or emphasis is on maintaining, protecting, or conserving something in its existing or intended state.
-
D.
stateOfPreservation
chosen
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
E.
preservationPurpose
Indicates that something exists, is created, or is maintained with the specific aim of preserving or safeguarding another entity or resource.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 7:18 p.m.