Triple
T10262645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Break My Soul |
E240635
|
entity |
| Predicate | featuresInterpolationOf |
P51626
|
FINISHED |
| Object | Explode |
—
|
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: Explode | Statement: [Break My Soul, featuresInterpolationOf, Explode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInterpolationOf Context triple: [Break My Soul, featuresInterpolationOf, Explode]
-
A.
interpolationOf
chosen
Indicates that one entity is derived by estimating intermediate values between known data points of another entity.
-
B.
interpolates
Indicates that one entity estimates or constructs intermediate values or states between known data points or conditions defined by another entity.
-
C.
featuresInversion
Indicates that one entity exhibits or incorporates an inversion of another entity, such as a reversed, mirrored, or otherwise inverted form or structure.
-
D.
featuresTransformationOf
Indicates that something includes or presents a transformation or change applied to another entity.
-
E.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:32 a.m.