Triple
T23023259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Over Her Dead Body |
E573225
|
entity |
| Predicate | featuresPsychicCharacter |
P150714
|
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: [Over Her Dead Body, featuresPsychicCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPsychicCharacter Context triple: [Over Her Dead Body, featuresPsychicCharacter, true]
-
A.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
B.
featuresCharacterWithSuperpowers
Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
-
C.
featuresNumberOfPersonalities
Indicates that an entity is characterized by or contains a specified number of distinct personalities.
-
D.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
E.
developmentCharacter
Indicates a relationship where one entity contributes to or influences the growth, formation, or evolution of another entity’s characteristics or qualities.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847b86688190b678d0d09ecd3c3d |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:52 p.m.