Triple
T17232374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma Carew |
E418272
|
entity |
| Predicate | romanticArcInvolves |
P103097
|
FINISHED |
| Object | tragedy |
—
|
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: tragedy | Statement: [Emma Carew, romanticArcInvolves, tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticArcInvolves Context triple: [Emma Carew, romanticArcInvolves, tragedy]
-
A.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
B.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
C.
romanticOutcome
chosen
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
D.
romanticTriangleInvolves
Indicates a romantic relationship structure in which three individuals are mutually or asymmetrically involved in overlapping romantic connections.
-
E.
romanticRivalryWith
Indicates a mutual competitive relationship in which two entities vie for the romantic attention or affection of the same person.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df7da748190a3a1762a67eb871b |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.