Triple
T16779838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalind Connage |
E407827
|
entity |
| Predicate | romanticArcType |
P118894
|
FINISHED |
| Object | doomed romance |
—
|
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: doomed romance | Statement: [Rosalind Connage, romanticArcType, doomed romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticArcType Context triple: [Rosalind Connage, romanticArcType, doomed romance]
-
A.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
B.
romanticPattern
chosen
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
C.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
D.
romanticAssociation
Indicates a romantic relationship or involvement exists between the associated entities.
-
E.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b214cebc81909de80e74b4bac5f8 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.