Triple
T26428902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris Simpkins |
E664446
|
entity |
| Predicate | breaksFreeFrom |
P72143
|
FINISHED |
| Object | toxic relationship with Jasper Bloom |
—
|
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: toxic relationship with Jasper Bloom | Statement: [Iris Simpkins, breaksFreeFrom, toxic relationship with Jasper Bloom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksFreeFrom Context triple: [Iris Simpkins, breaksFreeFrom, toxic relationship with Jasper Bloom]
-
A.
willBreakFreeDuring
Indicates that an entity is expected to escape or become free from another entity or constraint during a specified time or event.
-
B.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
C.
breaksUpIn
chosen
Indicates that one entity ends or dissolves a relationship or partnership with another entity.
-
D.
freeFrom
Indicates that one entity does not contain, is not affected by, or is exempt from another specified entity, condition, or constraint.
-
E.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611bc79f48190ad06b5264817251d |
completed | May 2, 2026, 3:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:47 p.m.