Triple
T12894319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wonders |
E308451
|
entity |
| Predicate | fictionalBreakupCause |
P107317
|
FINISHED |
| Object | creative differences |
—
|
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: creative differences | Statement: [The Wonders, fictionalBreakupCause, creative differences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalBreakupCause Context triple: [The Wonders, fictionalBreakupCause, creative differences]
-
A.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
B.
fictionalStepmother
Indicates a stepmother relationship that exists only within a fictional or narrative context.
-
C.
breakupProduced
Indicates that one entity was created or resulted from the breakup or disintegration of another entity.
-
D.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971484aa08190a8adfafabe600903 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.