Triple
T32101533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America’s Sweethearts |
E819862
|
entity |
| Predicate | featuresTrope |
P68123
|
FINISHED |
| Object | feuding lovers forced together |
—
|
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: feuding lovers forced together | Statement: [America’s Sweethearts, featuresTrope, feuding lovers forced together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTrope Context triple: [America’s Sweethearts, featuresTrope, feuding lovers forced together]
-
A.
usedAsTrope
chosen
Indicates that something functions as a recurring narrative device, motif, or cliché within a story or set of stories.
-
B.
tvtropesPage
Indicates that one entity is the TVTropes webpage corresponding to, describing, or cataloging the tropes of another entity.
-
C.
comicTrait
Indicates that an entity possesses a humorous or comedic characteristic, quality, or behavior.
-
D.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
E.
notableTraitInFiction
Indicates that a particular trait, characteristic, or quality is especially prominent or defining for an entity within fictional works.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: May 1, 2026, 12:26 a.m.