Triple
T14045015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ship to Wreck |
E337934
|
entity |
| Predicate | featuresThemes |
P26448
|
FINISHED |
| Object | self-destructive behavior |
—
|
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: self-destructive behavior | Statement: [Ship to Wreck, featuresThemes, self-destructive behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresThemes Context triple: [Ship to Wreck, featuresThemes, self-destructive behavior]
-
A.
featuresThemeType
Indicates that something (such as a work, event, or item) has or is characterized by a particular type of theme.
-
B.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
C.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
D.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
featuresTopic
chosen
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.