Triple
T27617608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Mitch Mitchell |
E700480
|
entity |
| Predicate | reasonForRelationshipBreakdown |
P35030
|
FINISHED |
| Object | Blanche DuBois’s troubled past |
—
|
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: Blanche DuBois’s troubled past | Statement: [Harold Mitch Mitchell, reasonForRelationshipBreakdown, Blanche DuBois’s troubled past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRelationshipBreakdown Context triple: [Harold Mitch Mitchell, reasonForRelationshipBreakdown, Blanche DuBois’s troubled past]
-
A.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
B.
breakupLinkedTo
chosen
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
-
C.
breakup
Indicates the ending or dissolution of a romantic or close personal relationship between two entities.
-
D.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
E.
brokeUpWith
Indicates that one entity ended a romantic or intimate relationship with 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 2:13 p.m.